Release v1.42.1 - #212
Merged
Merged
Conversation
SummaryPatch release v1.42.1 updates build/plugin versions, release documentation, and matching manifest tests. What looks good
Issues foundNone. The PR is clean and ready to merge. Test execution was blocked because the read-only environment could not create Go’s module cache. |
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.
Summary
Rationale
The merged #211 fix removes duplicate marketplace component declarations while keeping
.claude-plugin/plugin.jsonas the canonical owner of skills and hooks. This release aligns the CLI and both bundled plugin manifests with that compatibility fix.Validation
claude plugin validate .claude-plugin/marketplace.jsonclaude plugin validate .claude-plugin/plugin.json(only the known non-failing root-CLAUDE warning)git diff --checkmake ci(0 lint issues)make test-racemake release-checkfrom the clean committed branchRelease scope
This PR contains no tag, draft release, published release, or release assets. Publication remains a separate post-merge, gated operation.