Repository navigation
chore(release): prepare v0.5.6 - #1039
Merged
Merged
Conversation
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.
What was wrong
The package on main is still 0.5.5. The release workflow requires the tag to match the package version.
The change
Bump the package, lockfile and plugin manifest to 0.5.6. Roll over the changelog and add matching bilingual GitHub release notes. No runtime or dependency changes.
Validation
On Windows x64 with Node 24.18.0: npm ci --ignore-scripts and npm run build succeeded; manifest validation passed all 92 checks; source-size check passed all 865 files; git diff --check is clean. Cross-platform pull-request CI is required before merge.
Environment
Based on main at 863e367 (includes #1035).