chore(repo): Enter changesets Pre mode (for v5) #1970
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
| Name | Type |
|---|---|
| gatsby-plugin-clerk | Major |
| @clerk/clerk-js | Major |
| @clerk/clerk-sdk-node | Major |
| @clerk/backend | Major |
| @clerk/fastify | Major |
| @clerk/nextjs | Major |
| @clerk/shared | Major |
| @clerk/clerk-expo | Major |
| @clerk/types | Major |
| @clerk/chrome-extension | Patch |
| @clerk/remix | Patch |
| @clerk/clerk-react | Patch |
| @clerk/localizations | Patch |
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
dimkl
force-pushed
the
fix-version-packages
branch
3 times, most recently
from
0c9a367 to
387a803
Compare
dimkl
force-pushed
the
fix-version-packages
branch
from
387a803 to
3f83492
Compare
24 tasks
LekoArts
requested changes
Nov 1, 2023
dimkl
force-pushed
the
fix-version-packages
branch
3 times, most recently
from
629773b to
543e69b
Compare
LekoArts
reviewed
Nov 1, 2023
LekoArts
reviewed
Nov 1, 2023
LekoArts
changed the title
nikosdouvlis
approved these changes
Nov 1, 2023
dimkl
force-pushed
the
fix-version-packages
branch
2 times, most recently
from
4dbb3c7 to
aef6c94
Compare
LekoArts
approved these changes
Nov 1, 2023
dimkl
commented
Nov 1, 2023
Since we are using the pre-release changeset mode there is no need to generate canary releases upon merging commits to main using the `canary` related npm commands and gh actions. Also with this change we will stop producing a `canary` version on every main merge.
Since we have enabled the changeset pre-release mode the versions
produced by the Version packages PR will be pre-release tags with
a `alpha-v${next-major-version}` tag. So there is no need to block the Version Packages
PR from being merged and we will need to exit changeset pre-release
mode to release the stable next major version.
…be considered breaking
dimkl
force-pushed
the
fix-version-packages
branch
from
427ff92 to
db5a931
Compare
24 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Version packagesto produce next major version@alpha-v5releasemain-v4torelease/v4(are only used as reference for the future, those will actually be used to trigger flows when they are committed torelease/v4)To verify
premajortags:git checkout fix-version-packagesnpx changeset versionChecklist
npm testruns as expected.npm run buildruns as expected.Type of change
Packages affected
@clerk/backend@clerk/chrome-extension@clerk/clerk-js@clerk/clerk-expo@clerk/fastifygatsby-plugin-clerk@clerk/localizations@clerk/nextjs@clerk/clerk-react@clerk/remix@clerk/clerk-sdk-node@clerk/shared@clerk/themes@clerk/typesbuild/tooling/chore