Repository navigation
Complete 0.7.5 package-manager delivery - #157
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.
The 0.7.5 npm, crates, GitHub assets and MCP Registry publication succeeded, but Homebrew rejected the generated description's trailing full stop. Consume published mcp-kit 0.8.8, which normalizes Homebrew descriptions and preserves Scoop metadata.
Keep Lockdocs 0.7.5 and its canonical published artifacts unchanged. The shared release planner verifies and reuses delivered channels; the caller-owned package-manager job updates the existing release PR through normal checks/queue and reads back exact merged bytes. The workload's destination-only Broker policy is now Ready under the existing grant.
Validation: the shared regression fails before normalization, all21 renderer/publisher tests pass after it, and the shared kit's required CI and registry publication passed. Recovery is verified against the existing 0.7.5 artifacts and real destination installations after merge.