Add CI for unstable canary releases #91
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
* Identify the next semantic version by running regular release script (without changelog generation) * Bumps the version again, reusing the same semver version and adding a -commit suffix Nothing is committed during this script as it is intended to be used on CI only.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
chrisvxd
force-pushed
the
canary-releases
branch
from
e7cafa5 to
68bfd48
Compare
chrisvxd
changed the title
monospaced
requested changes
Sep 20, 2023
monospaced
approved these changes
Sep 20, 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.
This PR introduces 2 new types of release:
canaryon npm. Looks likev0.7.1-canary.aa5d202. This will enable us to test features merged tomainbefore finalising.pr - occurs on each PR build. Tagged withpron npm. Looks likev0.7.1-pr.aa5d202. This will allow us to test features in PRs before finalising the PR. Useful for testing generator changes.The semantic version is automatically calculated using the same tooling as the main release. No CHANGELOG is produced and currently no tag is produced either, otherwise each merge to master would result in a new tag.