Repository navigation
feat(release): publish npm nightlies with GitHub OIDC - #473
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
CLI Nightly currently produces an npm artifact but requires a separate manual publication. After
publish-nativesucceeds,release.ymlnow calls the reusable npm workflow with the immutable artifact ID and publishes through GitHub OIDC, preserving the release tag's source identity. Stable, RC and other applications do not publish to npm.The same workflow retains manual dry-run/recovery. It validates the source run and original artifact, reconciles existing versions by integrity, publishes at most once, and checks the public registry without downgrading
nightly. The daily coordinator reports a failed npm publication instead of treating a public GitHub archive as complete. The new behavior has a self-test in ordinary CI. Documentation now reflects the public npm package and tokenless configuration.Scope
Owner: harryisfish. Task: npm-trusted-publish-2026-11-06_17-08-51. Status: merged; pre-merge and post-merge CI passed.
This PR changes publication automation only. It does not include #472's CI optimizations or application behavior. Merged as 4a05387. No new release tag was created.
npm must separately trust both caller filenames (
release.ymlandnpm-publish.yml) inleaperone/vibeface, restricted to thenpm-releaseenvironment with publish permission. The maintainer confirmed both Trusted Publisher entries are configured. CLI readback still requires account MFA; actual OIDC, provenance and registry acceptance remain to be verified by the next CLI Nightly release.Verification
Post-merge CI passed for 4a05387: https://github.com/leaperone/vibeface/actions/runs/42199633738