chore: bump version to 3.2.1 - #45
Closed
JoshRobertson wants to merge 1 commit into
Closed
Conversation
package.json carried the semantic-release placeholder 0.0.0 while the latest published tag is v3.2.0. Set the real release version to 3.2.1 so package.json matches the intended v3.2.1 tag after the yarn 4.18 merge.
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.
Why
PR #44 merged the Yarn 4.18 upgrade. This aligns
package.jsonwith release tagging so the next publish is versioned correctly.package.jsonstill carried the semantic-release placeholder0.0.0, while the latest published git tag isv3.2.0. This sets the real release version to3.2.1, the next patch above the current tag.How it works
Single-line change:
package.jsonversion0.0.0→3.2.1. No code changes.Notes
Intended tag after merge: v3.2.1.