Skip to content

chore: bump version to 3.2.10#603

Merged
sunilgattupalle merged 2 commits into
mainfrom
chore/bump-version-3.2.10
Jul 10, 2026
Merged

chore: bump version to 3.2.10#603
sunilgattupalle merged 2 commits into
mainfrom
chore/bump-version-3.2.10

Conversation

@sunilgattupalle

Copy link
Copy Markdown
Collaborator

Summary

  • Bump package.json version to 3.2.10 ahead of the next release tag.

Test plan

  • CI passes (build, test, typecheck, docs:check)

AI-Session-Id: 103ece16-0d3e-4af0-a493-04e44aa113c9
AI-Tool: claude-code
AI-Model: unknown
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

cursor[bot]
cursor Bot approved these changes Jul 10, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked PR #603 for inline review comments to address — none found.

What I looked for:

  • Pull request review comments (/pulls/603/comments): 0
  • Review threads (GraphQL): 0 unresolved threads
  • PR reviews: none submitted yet

This PR only bumps package.json version from 3.2.9 to 3.2.10. No code changes were made.

I'll re-run when inline review feedback is posted on the diff.

Open in Web View Automation 

Sent by Cursor Automation: Autofix PR review comments

AI-Session-Id: 103ece16-0d3e-4af0-a493-04e44aa113c9
AI-Tool: claude-code
AI-Model: unknown

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Risk Assessment: Very Low (re-evaluated after update)

Decision: Existing approval retained — no reviewer assignment required.

Trigger

PR was updated (synchronize) after the initial approval. A second commit (99d5f886) synced manifest versions and updated the release-metadata test.

Evidence (diff-based)

Signal Finding
Files changed 4 (package.json, manifest.json, mcp-directory/manifest.json, tests/release-metadata.test.ts)
Lines changed +4 / −4
Production logic None — version fields only (3.2.93.2.10)
Test changes release-metadata.test.ts expectation updated to match synced versions
Infra / auth / security No impact
Blast radius None

Re-approval analysis

The new commit adds manifest version sync and a matching test assertion update. These are mechanical release-metadata changes with no behavioral, operational, or security surface change. Risk did not increase from the prior Very Low classification.

Per decision rules: approval is retained; no re-approval posted.

Actions taken

  • ✅ Re-evaluated — risk remains Very Low
  • ✅ Existing approval retained (risk unchanged)
  • ⏭️ No reviewers assigned (not required)
  • ℹ️ No CODEOWNERS file in repository
Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@sunilgattupalle sunilgattupalle merged commit 1860281 into main Jul 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants