chore(release): 2.3.0 - #13
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Bumps the package version to 2.3.0 for the corresponding release tag.
Changes:
- Updates the manifest version from 2.2.0 to 2.3.0.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
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
Step two of
RELEASING.md: the version bump that thev2.3.0tag will point at. It changes the one line and nothing else, so the tag resolves a commit whose manifest matches the tag name, which is what the publish workflow gates on.The editorial text landed in #12.
Validation
yarn run testpasses on a clearedexamples/node_modules: 35 unit tests plus the frozen examples install. That install is the one thing a version bump could have disturbed, sinceexamples/yarn.lockrecords the root package through afile:entry. It does not: yarn keys that entry on its pattern rather than on the resolved version, so the lockfile stays untouched and no lockfile edit rides along with the bump.