Repository navigation
chore: prepare v0.4.1 release - #10
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
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.
Prepare v0.4.1 after the readability fix in #9. Synchronize the plugin, runtime, project, lockfile, and issue-template versions; move Unreleased entries into a dated changelog section and add the release workflow's required notes.
The release includes #4–#7 already merged since v0.4.0 as well as #9. Issue #8 stays open until the tagged release and downloadable artifacts are verified. No additional runtime behavior changes are included here.
Validation: locked dependency sync,
validate_release.py --version 0.4.1, 37 release-script tests (1 skipped), and packaged MCP stdio smoke passed. The underlying fix passed all 15 CI checks before #9 was merged.