Skip to content

ci: move npm publish to GHA for trusted publishing with provenance#7061

Draft
serhalp wants to merge 5 commits into
mainfrom
claude/slack-session-78quP
Draft

ci: move npm publish to GHA for trusted publishing with provenance#7061
serhalp wants to merge 5 commits into
mainfrom
claude/slack-session-78quP

Conversation

@serhalp
Copy link
Copy Markdown
Member

@serhalp serhalp commented May 13, 2026

Summary

  • Move release.yml workflow (stable releases) from CircleCI to GitHub ACtions
  • Update pre-release.yml (already on GHA) to use OIDC permissions and --provenance flag

- Add release.yml workflow using release-please-action for stable releases
- Update pre-release.yml with OIDC permissions and --provenance flag
- Remove release-please job from CircleCI (update-lockfile stays)

https://claude.ai/code/session_011HCWQbTc6LTeMxgdwTH2R6
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 990eee6d-8505-4216-b211-d86f9aaf0a93

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/slack-session-78quP

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Comment thread .github/workflows/release.yml Outdated
serhalp and others added 2 commits May 13, 2026 12:06
With id-token: write permission and trusted publishing configured
on npmjs.com, npm uses the short-lived OIDC token automatically.
NODE_AUTH_TOKEN was bypassing OIDC and using the long-lived token.

https://claude.ai/code/session_01NmU7gnap9unNWgcsUyN3J7

publish:
needs: release-please
if: ${{ needs.release-please.outputs.releases_created == 'true' }}
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.

on npm publishing flakes when release-please run determine that release was created, but actual publish fails (i.e. some network or npm registry issues) this would mean there is no way to "retry" to actually publish to npm, so this is a change from the way CircleCi workflow works

Comment on lines +39 to +41
run: npx lerna publish from-package --yes --no-private
env:
NPM_CONFIG_PROVENANCE: true
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.

https://lerna.js.org/docs/recipes/oidc-trusted-publishing - not sure of details, but they say lerna 9 added support, but we use

"lerna": "^8.2.2",

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.

3 participants