🔖 (release): node-sdk 0.0.1-rc.3#228
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Claude Code — review record1. CI: ✅ all green (MERGEABLE; blocked only on required review). Verdict: Ready to merge. After merge → 🤖 Claude Code |
|
Claude Code — review record (updated: footprint completed)Earlier revision missed the docs footprint that rc.2 PR #205 established. Now complete (11 files):
CI: ✅ green. Side-effects: none. Verdict: ready to merge. 🤖 Claude Code |



What
Version-bump prep for the node-sdk 0.0.1-rc.3 release (coordinated with agent-assembly
v0.0.1-rc.3).package.jsonversion0.0.1-rc.2→0.0.1-rc.3sonar-project.propertiessonar.projectVersion→0.0.1-rc.3The 4
runtime-*sub-packages are intentionally not bumped here —release-node.ymlwrites their version from thenpm_versioninput at publish time (AAASM-2854); master keeps theworkspace:*markers.Why
Per the AAASM-3007 SOP (Case A): core
v0.0.1-rc.3cut,aa-ffi-nodepin PR (#225) merged (master pins fixed core3193b4c5). This bumps the SDK version literal so master is honest before the operator-drivenrelease-node.ymlworkflow_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.json→0.0.1-rc.3release-node.ymldry-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