[Snyk] Security upgrade @modelcontextprotocol/sdk from 1.24.1 to 1.25.2

[sestinj]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• core/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MODELCONTEXTPROTOCOLSDK-14871802	828

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

---

Continue Tasks

Status	Task	Actions
▶️ Queued	Create GitHub Issue (OS)	View

_{Powered by Continue}

---

Summary by cubic

Upgrades @modelcontextprotocol/sdk from 1.24.x to 1.25.2 in core/package.json to patch a high-severity ReDoS vulnerability (SNYK-JS-MODELCONTEXTPROTOCOLSDK-14871802).
No functional changes expected.

^{Written for commit db7d40b. Summary will update on new commits.}

[continue]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

---

Unsubscribe from All Green comments

[continue-staging]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

---

Unsubscribe from All Green comments

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ AI review failed. Please check the Continue API key and configuration.

Troubleshooting

• Verify the CONTINUE_API_KEY secret is set correctly
• Check that the organization and config path are valid
• Ensure the Continue service is accessible

---

[cubic-dev-ai]

No issues found across 1 file

[RomneyDa]

Failed to update package lock. Consolidating onto new PR