[AAASM-4067] 🐛 (release): Fix runtime npm publish path (./ prefix)#230
Conversation
…epo shorthand
release-node.yml passed a bare packages/${pkg} to npm publish; newer npm
parses it as a GitHub owner/repo spec and git-ls-remotes it over SSH instead
of publishing the local folder. ./ forces local-directory interpretation.
Refs AAASM-4067.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Claude Code — review record1. CI: ✅ no failing checks (workflow-file change). Verdict: Ready to merge. After merge → re-dispatch 🤖 Claude Code |



What
release-node.ymlline 379:npm publish ... "packages/${pkg}"→"./packages/${pkg}".Why
The rc.3 real publish (
publish_mode=all) failed at the first runtime sub-package:Newer npm parses the bare
packages/runtime-linux-x64as a GitHubowner/reposhorthand and tries to clone it over SSH instead of publishing the local folder. rc.2 published fine — GitHub-runner npm spec-parsing drifted (same runner-drift class as the core rc.3 break). The./prefix forces local-directory interpretation. Main SDK publish (line 404) has no path arg, so it's unaffected.Nothing reached npm in the failed run (runtime pkgs publish before the main SDK; first runtime pkg failed) — the
0.0.1-rc.3slot is intact.How to verify
Re-dispatch
release-node.yml(publish_mode=all,npm_version=0.0.1-rc.3) — the runtime loop publishes all 4@agent-assembly/runtime-*@0.0.1-rc.3+ main SDK. Closes AAASM-4067.🤖 Generated with Claude Code
https://claude.ai/code/session_01MvjnG3ysnqTY6Gu1wQ2h73