-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore(repo): Enable clerk@v5 release process #1837
Conversation
🦋 Changeset detectedLatest commit: 6110b0f The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
9e08961
to
5ee35f0
Compare
787a9db
to
b2014e3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this wait for #1854 to be merged as these scripts have changed a bit?
@nikosdouvlis i will rebase it and have it ready to merge after the #1854 |
b374800
to
0ea4ca6
Compare
7b98e6f
to
1d72b2d
Compare
Blocked by #1898 |
2dc5715
to
b60785d
Compare
7133b7a
to
2276921
Compare
Until clerk@v5 is ready for release we will be using the main-v4 branch for staging and production releases and every commit and changelog entry SHOULD be committed in both main-v4 and main branches. The main branch will be used to produce canary releases.
The main branch will produce canary releases until the next major version is ready for release. To produce a staging and production release, open a PR from the main-v4 branch.
2276921
to
6110b0f
Compare
This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
To prepare for the next major version (clerk@v5) we need to change our current release process.
Changes:
main-v4
branch to support releasing fixes and changes until next major version is ready for releasemain-v4
as the stable branch that producesstaging
andproduction
releasesmain
branch as the experimental branch that producescanary
releasesThecanary
releases broadcast messages toclerkinc/v5-testbench
that triggers a vercel preview releaseWhen next major version is stable and released the
staging
andproduction
releases will be produced from themain
branch. Themain-v4
will NOT be deleted until it's not considered LTS any more.This PR will be merged after those PRs are being merged: https://github.com/clerkinc/javascript/pulls?q=is%3Apr+is%3Aopen+label%3Av5-pre-release
Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change
Packages affected
@clerk/clerk-js
@clerk/clerk-react
@clerk/nextjs
@clerk/remix
@clerk/types
@clerk/themes
@clerk/localizations
@clerk/clerk-expo
@clerk/backend
@clerk/clerk-sdk-node
@clerk/shared
@clerk/fastify
@clerk/chrome-extension
gatsby-plugin-clerk
build/tooling/chore