Repository navigation
Release MASA tooling 0.2.3 with patched dependencies - #4
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 post-merge dependency audit reported new advisories in the MCP SDK, proxy-addr, and source-map-js. Update both SDK importers to 1.31.0 and the affected transitive packages to their patched releases. Advance synchronized reference tooling to 0.2.3 and regenerate its capabilities and conformance evidence; the normative MASA protocol remains 0.2.0.
Validation: fresh frozen installation, dependency audit with zero registry advisories, and the complete pnpm check gate pass, including schemas, 129 unit cases, all five conformance classes, package inspection and installed package smoke checks. The audit still excludes only the verified current local workspace importer collision.
The existing v0.2.2 tag stays immutable. This release does not publish packages to a registry.