Skip to content

Publish via npm Trusted Publisher (OIDC) instead of NPM_TOKEN - #3

Merged
Zechereh merged 1 commit into
mainfrom
zach/npm-trusted-publisher
Aug 4, 2026
Merged

Publish via npm Trusted Publisher (OIDC) instead of NPM_TOKEN#3
Zechereh merged 1 commit into
mainfrom
zach/npm-trusted-publisher

Conversation

@Zechereh

@Zechereh Zechereh commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Match the org's publish flow (ux-labs/.github/workflows/CD_sdk_typescript.yml): tokenless OIDC trusted publishing instead of an NPM_TOKEN secret.

  • workflow_dispatch escape hatch with a ref guard (main or v* tag only — a dispatch elsewhere goes red, not green-skip)
  • tag↔version assertion kept for tag-triggered runs
  • Node 24 in the publish job (npm ≥ 11.5 required for OIDC trusted publishing; consumers still need only Node ≥ 22)
  • build-output verification before publish; provenance comes automatically under trusted publishing

Requires (post-merge, one-time): first publish is manual (npm publish --access public by an org member — npm needs the package to exist before a trusted publisher can be configured), then add tinyfish-io/tinyfish-mcp-server + release.yml as the Trusted Publisher in the package settings on npmjs.com.

🤖 Generated with Claude Code

Match the org's CD_sdk_typescript.yml flow: tokenless OIDC publishing
with a ref guard and manual-dispatch escape hatch. Node 24 in the publish
job for npm >= 11.5 trusted-publishing support.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fa44522f-b1eb-404b-9419-3a1d8f9ae861

📥 Commits

Reviewing files that changed from the base of the PR and between 4aa162d and 0feeebe.

📒 Files selected for processing (1)
  • .github/workflows/release.yml

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

@Zechereh
Zechereh requested a review from KateZhang98 August 3, 2026 23:56
@Zechereh
Zechereh merged commit b4eb070 into main Aug 4, 2026
5 checks passed
@Zechereh
Zechereh deleted the zach/npm-trusted-publisher branch August 4, 2026 00:07
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