Skip to content

update release docs#78

Merged
simongdavies merged 1 commit intohyperlight-dev:mainfrom
simongdavies:update-docs
Apr 23, 2026
Merged

update release docs#78
simongdavies merged 1 commit intohyperlight-dev:mainfrom
simongdavies:update-docs

Conversation

@simongdavies
Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 23, 2026 16:10
@simongdavies simongdavies added the documentation Improvements or additions to documentation label Apr 23, 2026
@simongdavies simongdavies merged commit 1a7e37e into hyperlight-dev:main Apr 23, 2026
7 checks passed
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates release documentation to accurately reflect the current GitHub Actions publish pipeline and how versions are derived/injected for binaries and npm packages.

Changes:

  • Refreshes the “Automated Publishing” section to describe the split build/pack/publish workflow (self-hosted builds + GitHub-hosted publish for provenance).
  • Clarifies where the runtime/binary version comes from (build-time --define vs runtime git describe) and how npm package versions are set before npm pack.

Comment thread docs/RELEASING.md
2. Publishes npm package to [npmjs.org](https://www.npmjs.com/package/@hyperlight-dev/hyperagent) with [npm provenance](https://docs.npmjs.com/generating-provenance-statements) via OIDC trusted publishing
3. Publishes Docker image to GitHub Container Registry (`ghcr.io/hyperlight-dev/hyperagent`)
1. Builds native addons on Linux (KVM, glibc + musl) and Windows (WHP) self-hosted runners; runs tests on the KVM and WHP builds (musl is cross-compiled so it can't execute on the glibc host).
2. Packs a single cross-platform npm tarball on a self-hosted runner (needs the hyperlight toolchain), then publishes it from a **github-hosted** runner with [npm provenance](https://docs.npmjs.com/generating-provenance-statements) via OIDC trusted publishing. npm's sigstore backend rejects provenance from self-hosted runners (`E422 Unsupported GitHub Actions runner environment`), which is why the pack and publish steps are split.
Copy link

Copilot AI Apr 23, 2026

Choose a reason for hiding this comment

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

github-hosted should be capitalized as GitHub-hosted to match GitHub’s proper name and the rest of the document/workflow wording.

Suggested change
2. Packs a single cross-platform npm tarball on a self-hosted runner (needs the hyperlight toolchain), then publishes it from a **github-hosted** runner with [npm provenance](https://docs.npmjs.com/generating-provenance-statements) via OIDC trusted publishing. npm's sigstore backend rejects provenance from self-hosted runners (`E422 Unsupported GitHub Actions runner environment`), which is why the pack and publish steps are split.
2. Packs a single cross-platform npm tarball on a self-hosted runner (needs the hyperlight toolchain), then publishes it from a **GitHub-hosted** runner with [npm provenance](https://docs.npmjs.com/generating-provenance-statements) via OIDC trusted publishing. npm's sigstore backend rejects provenance from self-hosted runners (`E422 Unsupported GitHub Actions runner environment`), which is why the pack and publish steps are split.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants