• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

joaoh82 / rust_sqlite / 24935688717
69%

Build:
DEFAULT BRANCH: main
Ran 25 Apr 2026 04:49PM UTC
Jobs 1
Files 29
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

25 Apr 2026 04:45PM UTC coverage: 66.922%. Remained the same
24935688717

push

github

web-flow
release.yml: restore --provenance flag for npm OIDC publish (#34)

Second iteration of the publish-nodejs fix. The previous PR
(#32) cleared the wrong-thing-blocking-OIDC issue
(setup-node's registry-url generating an .npmrc that forced
token auth), but went too far by also removing the
`--provenance` flag based on docs that claim "no flags needed
for trusted publishers".

The v0.1.6 canary failed with:

  npm error code ENEEDAUTH
  npm error need auth This command requires you to be logged in
  to https://registry.npmjs.org/

ENEEDAUTH means npm CLI didn't even *try* OIDC token
exchange — it just looked for a configured _authToken, found
none, and gave up. Empirically, npm 11.5+ trusted publishing
*does* require `--provenance` to trigger the OIDC code path,
even though the official docs claim auto-detection.

Fix:
  - Restore `npm publish --provenance --access public`
  - Add `--loglevel verbose` so future auth/transport errors
    print enough detail to diagnose without re-running with
    debug logging on
  - Add a diagnostics step that prints whether
    ACTIONS_ID_TOKEN_REQUEST_URL +
    ACTIONS_ID_TOKEN_REQUEST_TOKEN are set (these are the
    GHA-injected env vars that OIDC depends on; if either is
    missing, OIDC can't possibly work and we want to see that
    in the log)
  - Updated the long inline comment block on the publish step
    to capture the *combined* understanding from PR #32 + this
    PR: registry-url removal + --provenance restoration are
    BOTH required, neither alone works

After this merges I'll dispatch v0.1.7 (v0.1.6 wave already
shipped 4 of 5 channels; the npm slot stays empty). The
diagnostic step will confirm OIDC env vars are present
regardless of whether publish succeeds or fails.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

4012 of 5995 relevant lines covered (66.92%)

1.23 hits per line

Jobs
ID Job ID Ran Files Coverage
1 24935688717.1 25 Apr 2026 04:49PM UTC 29
66.92
GitHub Action Run
Source Files on build 24935688717
  • Tree
  • List 29
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • b7f2f2a3 on github
  • Prev Build on main (#24929019302)
  • Next Build on main (#24935728315)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc