chore(release): use shared @protolabsai/release-tools action - #205
Merged
Conversation
Replaces the local `scripts/rewrite-release-notes.mjs` with the shared GitHub Action published from `protoLabsAI/release-tools`. Same script, same prompt, same gateway target — but now centralized so we don't copy-paste this between repos. Behavior parity: - Same model (`protolabs/fast`), same gateway URL (`https://api.proto-labs.ai/v1`), same Discord embed shape. - Same secrets read at the calling job's env: `GATEWAY_API_KEY` + `DISCORD_RELEASE_WEBHOOK`. - Same `--dry-run` toggle in `post-discord.yml`. - Squash-merge fallback (origin/dev commit window) is unchanged. Pinned to `v0.1.0`. Will bump as the action repo iterates; semver breaks land via deliberate version bumps here, not silently. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 0/5 reviews remaining, refill in 1 minute and 46 seconds. Comment |
Contributor
Code Coverage Summary
CLI Package - Full Text ReportCore Package - Full Text ReportFor detailed HTML reports, please see the 'coverage-reports-22.x-ubuntu-latest' artifact from the main CI run. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the loop: the local `scripts/rewrite-release-notes.mjs` we've been editing across the last few PRs (#181, #197, #201) is now the published `@protolabsai/release-tools` package. This PR deletes the local copy and swaps both call sites to the shared action.
Why
Other protoLabs repos want the same release ritual. Centralizing the script in protoLabsAI/release-tools (npm: @protolabsai/release-tools) means future repos drop in one workflow step instead of copy-pasting 240 lines of script + prompt.
Behavior parity
What changed
Pinned to `v0.1.0`. Action repo iterates independently; semver breaks land via deliberate version bumps here, not silently.
Test plan
🤖 Generated with Claude Code