Repository navigation
Release 5.6.1 - #60
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 the 5.6.1 maintenance release so the published container and MCPB bundle can pick up the merged dependency updates and plugin marketplace metadata fixes since 5.6.0.
Synchronize the package, lockfile, Claude plugin, Codex plugin, and Gemini extension versions, and add release notes. Merging this PR triggers the existing tag workflow; publishing waits for approval of the
releaseenvironment.Validation: production build, plugin metadata validation, npm package dry run, and whitespace checks passed. The combined dependency updates also passed all 43 tests before merging.