Skip to content

Release 2026-11-02.5: signed release assets - #39

Merged
qddegtya merged 4 commits into
mainfrom
release/2026-11-02.5
Nov 2, 2026
Merged

qddegtya merged 4 commits into
mainfrom
release/2026-11-02.5

Conversation

@qddegtya

@qddegtya qddegtya commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Release workflow attaches each release's tarball and provenance (#38); SECURITY.md explains verification. No package versions change.

🤖 Generated with Claude Code

qddegtya and others added 4 commits November 2, 2026 10:29
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chore: sync main into develop after release 2026-11-02.4
Every @hlang-org GitHub Release now carries the tarball it released
(checked against the registry's integrity hash), the Sigstore bundle of
the SLSA provenance npm recorded at publish time, and the in-toto
attestation inside it. Nothing is signed by the script; every file comes
from the registry. The step runs on every push to main and is idempotent,
so it also completes past releases; versions published before trusted
publishing have no provenance and are left as they are.

SECURITY.md explains how to verify a release, and its supported-versions
table now says runtime 2.x and interpreter 2.x.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ci(release): attach each release's tarball and provenance
@vercel

vercel Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
hlang Ready Ready Preview Nov 2, 2026 2:40am UTC

Request Review

@qddegtya
qddegtya merged commit ed8adf9 into main Nov 2, 2026
9 checks passed
@qddegtya
qddegtya deleted the release/2026-11-02.5 branch November 2, 2026 02:42
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.

1 participant