Skip to content

Record the unattended 0.1.2 publish #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sshlg merged 1 commit into from
Sep 27, 2026
Merged

Record the unattended 0.1.2 publish #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/evidence/releases/2026-09-28-npm/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,12 @@

A skipped or green-but-idle publish job proves nothing; the proof is an unpublished version
appearing on the registry from the tag alone.

## Observed after the tag

`v0.1.2` → release run 36359053252: jobs `validate`, `House skill audit`, `release` and
**`publish`** all `success` (the publish job ran, it did not skip). The registry then served
`dist-tags.latest = 0.1.2` with a SLSA v1 provenance attestation
(`npm view @ssheleg/web3d-dev@0.1.2 dist.attestations.provenance`). No token was used; the
publish authenticated through GitHub OIDC.

Loading