Skip to content

feat(release): publish npm nightlies with GitHub OIDC - #473

Merged
harryisfish merged 2 commits into
mainfrom
feat/npm-trusted-publish
Nov 6, 2026
Merged

harryisfish merged 2 commits into
mainfrom
feat/npm-trusted-publish

Conversation

@harryisfish

@harryisfish harryisfish commented Nov 6, 2026 •

Copy link
Copy Markdown
Collaborator

What changed

CLI Nightly currently produces an npm artifact but requires a separate manual publication. After publish-native succeeds, release.yml now 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.yml and npm-publish.yml) in leaperone/vibeface, restricted to the npm-release environment 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

  • Actionlint, publication/packaging/daily-coordinator self-tests and syntax checks pass. Tests cover original producer attempt reuse, invalid artifact identity, same-version retries, integrity conflicts, unavailable registry and lost publication responses.
  • All configured local preflight check/build and domain commands pass, including the static documentation site build. Independent review and final PR identity check pass.
  • Exact-head CI: https://github.com/leaperone/vibeface/actions/runs/42195392357 (completed successfully).
  • Actual OIDC exchange and a new public npm release have not been performed. Local checks and dry-run do not substitute for that acceptance.

Post-merge CI passed for 4a05387: https://github.com/leaperone/vibeface/actions/runs/42199633738

@harryisfish
harryisfish marked this pull request as ready for review November 6, 2026 10:02
@harryisfish
harryisfish merged commit 4a05387 into main Nov 6, 2026
23 checks passed
@harryisfish
harryisfish deleted the feat/npm-trusted-publish branch November 6, 2026 10:03
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