[AAASM-3459] 🔖 (release): node-sdk 0.0.1-beta.4 (prep)#168
Merged
Conversation
De-stales the local-dev package.json version from 0.0.1-alpha.4 to the next beta on the published line. The npm publish version is supplied at release time via release-node.yml (npm_version dispatch input); this field is local-dev metadata only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The quick-start install note still claimed the alpha line / alpha dist-tag and pinned an alpha example version, while the README already reflects the beta line. Sync it to beta to match the published line. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Chisanan232
commented
Jun 20, 2026
Chisanan232
left a comment
Contributor
Author
There was a problem hiding this comment.
Claude Code — PR review (AAASM-3459, node-sdk beta.4 prep)
✅ Ready to merge — release-prep only, no publish. CI all green (napi-build 20/22, build, quality, module-smoke, test matrix 18/20/22/24, CodeQL, SonarCloud).
- Correct version: npm
@beta = 0.0.1-beta.3→ next0.0.1-beta.4. De-stalespackage.jsonfrom the leftover0.0.1-alpha.4+ fixes the quick-start docs alpha→beta phrasing. - Correctly identified the published version is dispatch-set (
release-node.ymloverwritespkg.versionfromnpm_version/release_tag), so package.json is local-dev metadata; the 4 runtime sub-packages +optionalDependencies: workspace:*are workflow-rewritten at publish (left untouched here). versions.json/versionChannels.json left to the post-publish version-docs job. ✅ - No FFI-pin change (unchanged on master; the auto-bump PR handles it post-core-tag). Publish gating respected (no dispatch).
Good to merge as prep; publish stays gated on core v0.0.1-beta.3 + the FFI-pin bump.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Target
Task summary:
Version-prep for the next node-sdk beta on its published line. The published
npm
@agent-assembly/sdkbeta dist-tag is0.0.1-beta.3, so the nextbeta is 0.0.1-beta.4.
Source of truth — version is dispatch-set, not
package.json: thepublished npm version is supplied at release time via
release-node.yml(the
npm_versionworkflow_dispatchinput, or therelease_tagpayload onthe coordinated
repository_dispatchpath). The workflow overwritespackage.json'sversionat publish; master'sversionfield is local-devmetadata only. This PR therefore (1) de-stales that local field from the
leftover
0.0.1-alpha.4to0.0.1-beta.4, and (2) syncs the stalequick-start release-line note to the beta line. It does not drive the
publish.
Task tickets:
agent-assemblyv0.0.1-beta.3release + thebot/aa-ffi-pin-<tag>FFI-pin bump PR (per release-runbook SOP).Key point change (optional):
package.jsonversion:0.0.1-alpha.4→0.0.1-beta.4(de-stale).docs/02-quick-start/index.md: alpha note → beta note (0.0.1-beta.x,betadist-tag, beta pin example), matching the README.Effecting Scope
Action Types:
Scopes:
Additional description:
No code / public-API change. Publish is gated and not triggered by this
PR: the 5-package npm publish + native
aasmbinary are sourced from thecore
agent-assembly v0.0.1-beta.3GitHub Release (binary source +aa-sdk-clientFFI-pin). Perrelease-runbook/sdk-only-release, thecoordinated publish fires only after the core tag is cut and the
bot/aa-ffi-pin-<tag>bump PR is merged here. This PR does not dispatchrelease-node.yml.Description
package.jsonversion to0.0.1-beta.4.🤖 Generated with Claude Code