Skip to content

🔖 (release): node-sdk 0.0.1-rc.3#228

Merged
Chisanan232 merged 4 commits into
masterfrom
release/v0.0.1-rc.3
Jul 4, 2026
Merged

🔖 (release): node-sdk 0.0.1-rc.3#228
Chisanan232 merged 4 commits into
masterfrom
release/v0.0.1-rc.3

Conversation

@Chisanan232

Copy link
Copy Markdown
Contributor

What

Version-bump prep for the node-sdk 0.0.1-rc.3 release (coordinated with agent-assembly v0.0.1-rc.3).

  • root package.json version 0.0.1-rc.20.0.1-rc.3
  • sonar-project.properties sonar.projectVersion0.0.1-rc.3

The 4 runtime-* sub-packages are intentionally not bumped here — release-node.yml writes their version from the npm_version input at publish time (AAASM-2854); master keeps the workspace:* markers.

Why

Per the AAASM-3007 SOP (Case A): core v0.0.1-rc.3 cut, aa-ffi-node pin PR (#225) merged (master pins fixed core 3193b4c5). This bumps the SDK version literal so master is honest before the operator-driven release-node.yml workflow_dispatch (publish_mode=all) publishes @agent-assembly/sdk@0.0.1-rc.3 + 4 runtime sub-packages to npm.

How to verify

  • jq -r .version package.json0.0.1-rc.3
  • After merge: release-node.yml dry-run then real (npm_version=0.0.1-rc.3, binary_source_tag=v0.0.1-rc.3, publish_mode=all).

Version literals only — no source/behavior change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MvjnG3ysnqTY6Gu1wQ2h73

@codecov

codecov Bot commented Jul 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@Chisanan232

Copy link
Copy Markdown
Contributor Author

Claude Code — review record

1. CI: ✅ all green (MERGEABLE; blocked only on required review).
2. Scope: ✅ version-bump prep only — root package.json 0.0.1-rc.2→0.0.1-rc.3, sonar-project.properties→0.0.1-rc.3. Runtime sub-packages correctly untouched (workflow bumps them from npm_version at publish, AAASM-2854). Two granular commits.
3. Side-effects: ✅ none — version literals only. aa-ffi-node core pin (fixed 3193b4c5, from #225) untouched.

Verdict: Ready to merge. After merge → release-node.yml dry-run then real (npm_version=0.0.1-rc.3, binary_source_tag=v0.0.1-rc.3, publish_mode=all) publishes @agent-assembly/sdk + 4 runtime sub-packages to npm.

🤖 Claude Code

@sonarqubecloud

sonarqubecloud Bot commented Jul 4, 2026

Copy link
Copy Markdown

@Chisanan232

Copy link
Copy Markdown
Contributor Author

Claude Code — review record (updated: footprint completed)

Earlier revision missed the docs footprint that rc.2 PR #205 established. Now complete (11 files):

  • root package.json + sonar-project.properties → 0.0.1-rc.3
  • docs/02-quick-start/index.md + docs/09-examples/*.md (7) SDK version pins → 0.0.1-rc.3
  • .claude/skills/sdk-only-release/SKILL.mdadded the prep-PR footprint section (same root cause as python-sdk); documents what NOT to touch too (runtime-* sub-packages, pnpm-lock, website/versioned_docs).

CI: ✅ green. Side-effects: none. Verdict: ready to merge.

🤖 Claude Code

@Chisanan232 Chisanan232 merged commit d3f4cf8 into master Jul 4, 2026
27 checks passed
@Chisanan232 Chisanan232 deleted the release/v0.0.1-rc.3 branch July 4, 2026 00:27
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.

1 participant