chore: release v1.0.0#3
Conversation
Stabilizes the API now that consumers will pin to @v1: - @protolabsai/release-tools npm package gains the build-updater-manifest binary alongside rewrite-release-notes - New reusable workflow at .github/workflows/tauri-release.yml exposes the full sign + notarize + R2 publish pipeline as a workflow_call interface The reusable workflow's input + secret contract is the new public surface; bumping to 1.x signals consumers can pin to @v1 with the expectation of additive-only changes within the major. 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 0/5 reviews remaining, refill in 3 minutes and 24 seconds. Comment |
1 participant
Summary
Bumps to v1.0.0, signaling API stability for the new consumer surface added in #2.
The release workflow triggers on `chore: release v*` commits to main, so squash-merging this PR (with this title) will:
After it lands, I'll push a moving `v1` tag pointing at the same commit so consumers can pin to `@v1` and get patch/minor updates automatically. (mythxengine's `build-desktop.yml` will reference `@v1` once #326 lands.)
Why a major bump
Pre-1.0 (0.x) bumps signal an unstable surface. With #2 adding the reusable workflow + the second exported binary, the API contract is now what new consumers (mythxengine, future protoLabs desktop apps) will pin to. 1.x is the explicit promise that within `@v1` we'll only add additive changes.
Test plan
🤖 Generated with Claude Code