Release v6.9.3 - #62
Merged
Merged
Conversation
Contributor
Contributor
|
✅ Reviewed the changes: Straightforward version bump to 6.9.3, but package-lock.json still pins 6.9.2 — the release workflow's |
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.
Release v6.9.3
Version-bump-only release so the publish runs from a
release/vX.Y.Zbranch (therelease/6.9.2PR merged earlier didn't match the workflow'srelease/v*head-ref gate; v6.9.2 itself was already published via #60).Changed
package.json+package-lock.jsonadvanced to6.9.3, changelog section added.Validation
release/v6.9.3matches the workflow'srelease/vX.Y.Zpattern andpackage.jsonversion (6.9.3) — satisfies the release.yml version check.npm publish+ GitHub Releasev6.9.3will run on merge.