Repository navigation
Verify npm registry integrity after accepted beta publication - #18
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
|
Verification: changed workflow passes actionlint; actual post-publish registry verification shell passed against the published beta.9 tarball and its sha512 integrity. Hosted npm-package CI gate passed. supplementary/chart remain queued because repository runner coordinator-runners-runner-8fdrk is offline (runner API checked). Leaving this PR unmerged rather than bypassing the existing gates. npm-public workflow dispatch and beta channel are unchanged; owner-side current npm trusted publisher/environment settings are not accessible from this session. |
Retains exact-source CI artifact checks, OIDC, npm-public environment and explicit beta dispatch. Adds post-publication registry version and sha512 integrity verification before success reporting. Actionlint passed for the changed workflow. The actual new verification shell passed against downloaded beta.9 registry artifact; no npm publication performed. Owner-side current npm trust/environment settings remain unverified.