fix(release): ship the version master is actually on - #246
Merged
Conversation
2.6.0 published before the package check moved into CI and before docs/releasing.md existed, so npm and master disagree on what 2.6.x contains. The commits since were ci and docs only, which the version script correctly releases nothing for. fix, so a version gets cut and the two agree again.
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.
2.6.0 published before
check:packagemoved into CI (#245) and beforedocs/releasing.mdexisted, so npm and master disagree about what 2.6.x contains. The commits since werecianddocsonly, which the version script correctly releases nothing for.fix, so a version gets cut and the two agree again.🤖 Generated with Claude Code