chore: add npm release automation#2
Conversation
|
Warning Review limit reached
More reviews will be available in 3 minutes and 46 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
📝 WalkthroughWalkthroughAdds Release Please automation for the ChangesRelease Automation Setup
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
53fedf0 to
4e441ce
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/release.yml:
- Around line 57-74: The "Append OpenCode summary to GitHub release" step is
missing the `continue-on-error: true` configuration. Add `continue-on-error:
true` to this step definition so that if the gh release edit command fails, the
workflow continues to the next step instead of blocking the npm publish step.
This ensures that external service failures do not prevent the publication
process.
In `@scripts/summarize-release-diff.mjs`:
- Around line 80-87: Add a timeout option to the spawnSync call that invokes npx
opencode-ai. Include a reasonable timeout value in milliseconds within the
options object (the third parameter) alongside the existing encoding and env
properties. Additionally, update the error handling logic after the spawnSync
call to check not only for result.status but also for timeout errors by
verifying if result.error?.code === 'ETIMEDOUT', and handle this timeout case
appropriately by logging an error and exiting the process to prevent the release
job from hanging indefinitely.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 957ee15f-4b7d-4887-a8a4-ab5c1ffb2423
📒 Files selected for processing (7)
.github/workflows/release.yml.release-please-manifest.jsonAGENTS.mdREADME.mdpackage.jsonrelease-please-config.jsonscripts/summarize-release-diff.mjs
✅ Files skipped from review due to trivial changes (3)
- .release-please-manifest.json
- README.md
- release-please-config.json
🚧 Files skipped from review as they are similar to previous changes (1)
- package.json
153e27c to
55cc2ab
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/release.yml:
- Around line 35-38: In the `actions/setup-node` action configuration, add a new
line `package-manager-cache: false` to the with section to explicitly disable
automatic npm caching. This prevents potential cache-poisoning attacks in the
privileged publish job that has `id-token: write` permissions. The property
should be added alongside the existing `node-version` and `registry-url`
configuration properties.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a3f37b43-9e05-45ce-bd25-6711d9d12381
📒 Files selected for processing (7)
.github/workflows/release.yml.release-please-manifest.jsonAGENTS.mdREADME.mdpackage.jsonrelease-please-config.jsonscripts/summarize-release-diff.mjs
✅ Files skipped from review due to trivial changes (2)
- .release-please-manifest.json
- release-please-config.json
🚧 Files skipped from review as they are similar to previous changes (3)
- README.md
- package.json
- scripts/summarize-release-diff.mjs
55cc2ab to
cdb7098
Compare
Summary
Validation
Required npm setup before first publish
Configure npm trusted publishing for package sidc-kit:
No NPM_TOKEN is needed for this workflow.
Summary by CodeRabbit
Release Notes
Documentation
New Features
Chores
mainto create GitHub releases and publish to npm.