All five packages (@arcp/sdk, @arcp/client, @arcp/core, @arcp/runtime, @arcp/middleware-*) are at 0.1.0 locally and npm view @arcp/sdk version returns E404 — they are not on the registry.
Steps:
- Bump versions per
CHANGELOG.md if not already
- Confirm
.github/workflows/publish.yml is fixed (see related issue) — it should be the publish path
- Tag a release:
gh release create v0.1.0 --generate-notes (or chosen version)
- Verify each package lands:
npm view @arcp/sdk @arcp/client @arcp/core @arcp/runtime version
- Update README install snippet if needed
The TS SDK is the reference implementation; an unpublished reference makes downstream SDKs harder to consume.
Audit reference: ARCP SDK Audit v1.1 (2026-05-19)
All five packages (
@arcp/sdk,@arcp/client,@arcp/core,@arcp/runtime,@arcp/middleware-*) are at0.1.0locally andnpm view @arcp/sdk versionreturns E404 — they are not on the registry.Steps:
CHANGELOG.mdif not already.github/workflows/publish.ymlis fixed (see related issue) — it should be the publish pathgh release create v0.1.0 --generate-notes(or chosen version)npm view @arcp/sdk @arcp/client @arcp/core @arcp/runtime versionThe TS SDK is the reference implementation; an unpublished reference makes downstream SDKs harder to consume.
Audit reference: ARCP SDK Audit v1.1 (2026-05-19)