Skip to content

ci: npm trusted publishing and release 0.9.2 - #43

Merged
devinpearson merged 2 commits into
mainfrom
fix/npm-trusted-publishing
Aug 3, 2026
Merged

ci: npm trusted publishing and release 0.9.2#43
devinpearson merged 2 commits into
mainfrom
fix/npm-trusted-publishing

Conversation

@devinpearson

@devinpearson devinpearson commented Aug 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • Publish with npm Trusted Publishing (OIDC) instead of long-lived NPM_TOKEN
  • Add workflow_dispatch so a tag can be re-published after trusted publisher setup
  • Bump version to 0.9.2 and update README download URLs

Test plan

  • Merge this PR
  • Tag and push v0.9.2 (or run Publish to npm with tag v0.9.2)
  • npm view investec-ipb version shows 0.9.2

Drop NPM_TOKEN from the publish step so GitHub Actions authenticates with the configured trusted publisher. Add workflow_dispatch so the v0.9.1 tag can be re-published after setup.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 11 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 Plus

Run ID: 716a8e25-5aca-4384-bf0d-48af88bf35e0

📥 Commits

Reviewing files that changed from the base of the PR and between d4c0380 and 17cbf82.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • .github/workflows/publish.yml
  • README.md
  • package.json

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.

Co-authored-by: Cursor <cursoragent@cursor.com>
@devinpearson devinpearson changed the title ci: use npm trusted publishing for releases ci: npm trusted publishing and release 0.9.2 Aug 3, 2026
@devinpearson
devinpearson merged commit 087943a into main Aug 3, 2026
4 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.

1 participant