Skip to content

Add trusted npm publishing with provenance - #2

Merged
kbaghini merged 1 commit into
masterfrom
agent/trusted-publishing
Jul 19, 2026
Merged

Add trusted npm publishing with provenance#2
kbaghini merged 1 commit into
masterfrom
agent/trusted-publishing

Conversation

@kbaghini

Copy link
Copy Markdown
Owner

Summary

Adds npm trusted publishing to the version-tag release workflow.

Why

Trusted publishing uses GitHub OIDC instead of a long-lived npm token and automatically creates package provenance for public packages.

Behavior

For a pushed v* tag, the workflow now:

  1. Installs and tests the exact tagged source.
  2. Verifies the package tarball.
  3. Rejects tags that do not match package.json.
  4. Publishes through npm trusted publishing, or safely recognizes an already-published exact version.
  5. Creates the matching GitHub Release.

The workflow cannot publish until the npm package is configured to trust kbaghini/node-idb and .github/workflows/release.yml.

Validation

  • 41 tests passed
  • Package dry-run passed
  • Workflow and documentation formatting passed

@kbaghini
kbaghini marked this pull request as ready for review July 19, 2026 14:01
@kbaghini
kbaghini merged commit ac4dceb into master Jul 19, 2026
6 checks passed
@kbaghini
kbaghini deleted the agent/trusted-publishing branch July 19, 2026 14:01
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