fix: publish canary releases with the calculated next version instead of 0.0.0 - #278
Open
beeman wants to merge 1 commit into
Open
fix: publish canary releases with the calculated next version instead of 0.0.0#278beeman wants to merge 1 commit into
beeman wants to merge 1 commit into
Conversation
|
commit: |
… of 0.0.0 Canary snapshots were published as 0.0.0-canary-<timestamp>, which hides which release the canary previews. With snapshot.useCalculatedVersion the pending changesets are applied first, so a canary now reads e.g. 4.9.0-canary-<timestamp>.
beeman
force-pushed
the
beeman/canary-calculated-version
branch
from
August 7, 2026 13:51
5222157 to
fe4de77
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Canary snapshots were published as
0.0.0-canary-<timestamp>, which hides which release the canary previews. Withsnapshot.useCalculatedVersionthe pending changesets are applied first, so a canary now reads e.g.4.9.0-canary-<timestamp>.