Repository navigation
Conversation
The release job published with the org NPM_TOKEN secret, which npm now rejects (E404 on PUT for 7.0.6). The job now authenticates with npm trusted publishing: npm exchanges the job's GitHub OIDC token for a short-lived publish token and adds a provenance attestation. Same setup as dashpay/dashcore-lib#326: only GitHub's own actions, pinned to commits, run in the job that holds id-token: write, the tag checks are plain shell, and nothing is installed before publishing. package.json's repository now names dashpay/dashcore-node, which provenance requires. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7.0.6 never reached npm. 7.0.7 is the first release published with trusted publishing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Problem
The v7.0.6 release never reached npm. Its release job, and the re-run on 2026-11-20, failed at
npm publishwithE404 Not Found - PUT https://registry.npmjs.org/@dashevo%2fdashcore-node: the orgNPM_TOKENsecret (last updated 2022) can no longer publish. Insight on Dash Core v24 networks needs this release.Changes
NPM_TOKENis no longer used. The job is a copy of ci: publish to npm with trusted publishing dashcore-lib#326, which published dashcore-lib 0.26.1 this way:permissions: contents: read, id-token: writeon the release job only;geritol/match-tag-to-package-versionandactions/github-script;npm publish --ignore-scripts, so no package script runs while the OIDC token is available. The tarball has the same 77 files as 7.0.5.--loglevel verbose, the only level at which npm logs why an OIDC exchange failed.package.jsonnamesdashpay/dashcore-node(repository,bugs,homepage). Provenance requiresrepository.urlto match the repository that publishes.The npm trusted publisher for
@dashevo/dashcore-nodeis configured:dashpay/dashcore-node,test_and_release.yml, no environment,npm publishallowed. It has to publish once before 2026-11-22 14:52 UTC or it must be re-created.After merge
Publish GitHub release v7.0.7 from
master, then checknpm view @dashevo/dashcore-node versionand the provenance on npmjs.com. The release job does not run in PR CI, so the release is its first run.🤖 Generated with Claude Code
Summary by CodeRabbit
latesttag. Release tags must match the package version.