chore: update release 1.1301.2 #6382
Merged
+8
−27
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
Merge pull request #6355 from snyk/release-candidate
A bug was introduced in github.com/mark3labs/mcp-go v0.43 that is used in the studio-mpc v1.1.0 updateing studio-mcp to v1.1.1 which uses the previous good github.com/mark3labs/mcp-go v0.31
fix: [AG-99] mcp spec compliance fix
CatalinSnyk
reviewed
Dec 15, 2025
| @@ -1,11 +1,7 @@ | |||
| ## [1.1301.1](https://github.com/snyk/snyk/compare/v1.1301.0...v1.1301.1) (2025-12-08) | |||
| ## [1.1301.2](https://github.com/snyk/snyk/compare/v1.1301.0...v1.1301.1) (2025-12-16) | |||
Collaborator
There was a problem hiding this comment.
nit: the compare ranges are not updated, but at this point we can probably do it after the release
CatalinSnyk
approved these changes
Dec 15, 2025
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Where should the reviewer start?
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?