Skip to content

fix(release): restore npm publish credentials - #99

Merged
drewstone merged 1 commit into
mainfrom
fix/release-token-fallback-20260902
Sep 2, 2026
Merged

fix(release): restore npm publish credentials#99
drewstone merged 1 commit into
mainfrom
fix/release-token-fallback-20260902

Conversation

@drewstone

Copy link
Copy Markdown
Contributor

Summary

  • restore the existing NPM_TOKEN repository secret for the npm publish step
  • preserve npm provenance generation
  • update the release workflow contract test

The v0.12.3 tag and package contents are unchanged. This restores the repository's existing publish path while npm trusted publishing remains unconfigured.

Checks

  • pnpm typecheck
  • pnpm test (683 passed)
  • pnpm build
  • pnpm check:package
  • pnpm exec vitest run tests/publish-workflow.test.ts

@tangletools tangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved drewstone PR — 24967769

This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

This approval is provisional. It rests on the audit running. If the audit cannot run — for example the CLI bridge rejects it — this approval is dismissed rather than left standing, so an unrun check never reads as a passing one.

tangletools · auto-approval · reason: drewstone_author · 2026-09-02T05:03:41Z

@drewstone
drewstone merged commit dd8c157 into main Sep 2, 2026
2 checks passed
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