Skip to content

chore(release): use npm trusted publishing for scip-python releases - #235

Merged
chrapkowski-sg merged 1 commit into
scipfrom
release-trusted-publishing
Oct 22, 2026
Merged

chrapkowski-sg merged 1 commit into
scipfrom
release-trusted-publishing

Conversation

@chrapkowski-sg

Copy link
Copy Markdown
Collaborator

The v0.6.7 release run (39689663660) failed at npm publish with ENEEDAUTH: secrets.NPM_TOKEN resolves to empty, so the Docker image for INC-541 (#233) was never pushed.

This switches the release job to npm trusted publishing (OIDC), the same change scip-typescript made in sourcegraph/scip-typescript#511 and #514, whose v0.5.1 release succeeded today:

  • id-token: write permission for the job
  • Node 16 → 24 (trusted publishing needs npm ≥ 11.5.1; Node 24 bundles npm 11)
  • drop registry-url and NODE_AUTH_TOKEN

Before merging: the npm package @sourcegraph/scip-python must have a trusted publisher configured for repository sourcegraph/scip-python and workflow scip-release.yml.

Docker Hub login still uses DOCKER_USERNAME / DOCKER_PASSWORD. scip-typescript reads these from org-level secrets and they worked for its v0.5.1 release.

The release job has no NPM_TOKEN secret, so npm publish fails with
ENEEDAUTH and the Docker image is never pushed. Publish with npm
trusted publishing (OIDC) like scip-typescript (#511, #514). Node 24
ships npm 11, which trusted publishing requires.

Amp-Thread-ID: https://ampcode.com/threads/T-01a16041-ef1e-774a-957e-9f7122a62a0e
Co-authored-by: Amp <amp@ampcode.com>
@chrapkowski-sg
chrapkowski-sg merged commit f8b65fa into scip Oct 22, 2026
5 checks passed
@chrapkowski-sg
chrapkowski-sg deleted the release-trusted-publishing branch October 22, 2026 00:47
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.

2 participants