chore: circleci setup to allow pre-release on next branch [SPA-1634] #176
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
Spring3
requested review from
elylucas,
primeinteger,
chasepoirier,
ryunsong-contentful and
a team
Spring3
changed the title
- @contentful/experience-builder@3.0.0 - @contentful/experience-builder-types@2.0.0
- @contentful/experience-builder@3.0.1 - @contentful/experience-builder-types@2.0.1
primeinteger
approved these changes
Dec 7, 2023
Chaoste
approved these changes
Dec 8, 2023
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.
To enable us to accumulate changes for the next major version, I created a
nextbranch and here I am adding configuration to have lerna release new changes as pre-releaseWe'd have to keep
mainandnextin sync from time to time, which we can do via github actions laterTicket with some planned changes before major (not pre-release) release