fix(sdk): validate release version consistency for 0.3.1

[777genius]

The SDK draft build failed because its metadata test still required version 0.2.4 after the package moved to 0.3.0. Validate stable SemVer and package/lock name and version consistency instead.

Prepare SDK 0.3.1 for a new draft while preserving the existing 0.3.0 tag and failed build evidence. No runtime behavior or dependency versions change.

Validation: original failure reproduced; all 352 SDK tests passed on Node 24.18.0, including localhost tests outside the worker sandbox. Independent Sol xhigh review found no actionable P1/P2; separately reproduced 11 manifest tests. No release published.

Summary by CodeRabbit

• Release
  • Updated the TypeScript SDK package version to 0.3.1.
  • Improved release validation to support stable three-part semantic versions and ensure package metadata remains consistent.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: cb506611-9922-44c5-b9dc-e73ed0e48de3

📥 Commits

Reviewing files that changed from the base of the PR and between 43b1256 and 70775f4.

⛔ Files ignored due to path filters (1)

• packages/infinity_context_ts_sdk/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• packages/infinity_context_ts_sdk/package.json
• packages/infinity_context_ts_sdk/tests/sdk-release-manifest.test.mjs

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The SDK package version changed from 0.3.0 to 0.3.1. The release manifest test now validates stable SemVer and checks package and lockfile identity and version consistency.

Changes

SDK release metadata

Layer / File(s)	Summary
Version and manifest validation packages/infinity_context_ts_sdk/package.json, packages/infinity_context_ts_sdk/tests/sdk-release-manifest.test.mjs	The package version is 0.3.1. The test accepts stable three-part SemVer and validates package and lockfile names and versions.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 70775

The SDK metadata update is consistent with the repository's release-version contract and is ready to merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main changes: SDK release version consistency validation and preparation for version 0.3.1.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/sdk-release-version-assertion

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the version line
Three neat numbers now align
The lockfile hops beside the pack
Stable checks keep errors back
The SDK wears 0.3.1
Release time has begun!}

_{Comment @coderabbitai help to get the list of available commands.}