Skip to content

chore: use npm trusted publishing#532

Merged
tarrencev merged 1 commit into
mainfrom
chore/npm-trusted-publishing
Jul 10, 2026
Merged

chore: use npm trusted publishing#532
tarrencev merged 1 commit into
mainfrom
chore/npm-trusted-publishing

Conversation

@tarrencev

Copy link
Copy Markdown
Contributor

Summary

  • publish npm packages through GitHub Actions OIDC instead of a long-lived NPM_TOKEN
  • run the npm CLI from Node 24 and enable provenance attestations
  • preserve release commits, tags, and downstream release workflow dispatch permissions

npm configuration required

Before running a real release, configure a GitHub Actions Trusted Publisher on each of the nine public packages with:

  • Organization: dojoengine
  • Repository: dojo.js
  • Workflow: release.yaml
  • Environment: blank

Packages: core, create-burner, create-dojo, grpc, predeployed-connector, react, sdk, state, and utils.

Validation

  • actionlint .github/workflows/release.yaml
  • Prettier check
  • git diff --check origin/main...HEAD

The previous token-backed release attempts failed npm authentication before any package, release commit, or tag was created.

@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@tarrencev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: b56298e4-424e-46d5-8cd2-91e5f3731d0a

📥 Commits

Reviewing files that changed from the base of the PR and between 475b7ac and 4012f13.

📒 Files selected for processing (1)
  • .github/workflows/release.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/npm-trusted-publishing

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.

@tarrencev tarrencev changed the title ci: use npm trusted publishing chore: use npm trusted publishing Jul 10, 2026
@tarrencev tarrencev merged commit 6cfa5c5 into main Jul 10, 2026
9 of 10 checks passed
@tarrencev tarrencev deleted the chore/npm-trusted-publishing branch July 10, 2026 18:14
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