Skip to content

release: 1.0.0 (first stable) - #19

Merged
gavin09527 merged 3 commits into
mainfrom
release/v1.0.0
Jul 20, 2026
Merged

release: 1.0.0 (first stable)#19
gavin09527 merged 3 commits into
mainfrom
release/v1.0.0

Conversation

@gavin09527

Copy link
Copy Markdown
Collaborator

Promote @openmaxai/openmax-agent-sdk from 0.1.0-alpha.31.0.0 (first stable).

  • main already contains the token-cache root fix (fix(token): bind cached JWT to the api_key that minted it (fix wrong-identity on api_key swap) #18): cached JWT is bound to the api_key fingerprint and re-exchanged on mismatch (fixes wrong-identity on api_key swap within an org).
  • Version bumped in package.json + package-lock.json only (no code change here).
  • After merge, tagging v1.0.0 triggers the release workflow → npm publish --provenance to the latest dist-tag (1.0.0 has no hyphen), gated on the protected release environment (human approval).

🤖 Generated with Claude Code

fix #18)

Promotes @openmaxai/openmax-agent-sdk from 0.1.0-alpha.3 to the first
stable 1.0.0. main already contains the token-cache identity fix (#18).
Tagging v1.0.0 after merge publishes to the npm `latest` dist-tag.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@zylos-luna-coco zylos-luna-coco left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version-bump only: 0.1.0-alpha.31.0.0, no code change. Verified:

  • main contains #18 (token-cache root fix) — c189286 is HEAD.
  • Dist-tag logic correct: 1.0.0 has no hyphen → DIST_TAG="latest" per release.yml:59. The pre-stable alpha→latest convenience block (release.yml:63-77) will no-op since DIST_TAG != "alpha". Bare npm install @openmaxai/openmax-agent-sdk will resolve 1.0.0 from this point forward.
  • Ancestry gate (release.yml:25-31): tag must be on main, so only code that passed branch protection review can be published — supply chain sound.
  • Protected release environment gates the publish behind human approval — no accidental pushes.

LGTM.

gavin09527 and others added 2 commits July 20, 2026 14:51
…#19 review)

- src/index.js: SDK_VERSION now derived from package.json via createRequire
  (single source of truth) instead of a hardcoded '0.1.0-alpha.0' — was a
  runtime-visible version drift; now can't recur.
- README: install command drops the `@alpha` tag, obsolete 'no stable release
  yet' warning replaced with a 1.0.0-stable note, Status bumped to 1.0.0.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Bring the release branch up to date with main so the 1.0.0 release includes
the newly-added PR-triggered CI (SAST/secret-scan/tests) and the Semgrep
finding fixes (shell-injection env-indirection + rule-specific nosemgrep).
No file overlap with the version bump → conflict-free.

@zylos-luna-coco zylos-luna-coco left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-approved after update (head 25f581f). New additions since last review:

  • README: Installation section updated for 1.0.0 (removes @Alpha caveat, notes alpha dist-tag for history). Status section updated. Correct.
  • SDK_VERSION: now createRequire(import.meta.url)('../package.json').version instead of a hardcoded string — eliminates version drift between package.json and the exported constant. createRequire is the standard ESM pattern for reading JSON; correct.

Combined with the original version bump, this is a complete 1.0.0 release PR. LGTM.

@gavin09527
gavin09527 merged commit faefd38 into main Jul 20, 2026
4 checks passed
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.

2 participants