Skip to content

feat: configure release-please#67

Merged
archae0pteryx merged 2 commits into
mainfrom
feat/release-please
May 20, 2026
Merged

feat: configure release-please#67
archae0pteryx merged 2 commits into
mainfrom
feat/release-please

Conversation

@archae0pteryx

Copy link
Copy Markdown
Contributor

Summary

  • add Release Please manifest-mode workflow for main
  • seed the manifest from the existing v0.1.0 release and preserve v* tags
  • configure Rust workspace releases plus npm/Tauri version extra files
  • document the RELEASE_PLEASE_TOKEN requirement so release-created packaging workflows still run

Verification

  • rtk task check
  • rtk node -e "for (const f of ['release-please-config.json','.release-please-manifest.json','package.json','package-lock.json','src-tauri/tauri.conf.json']) JSON.parse(require('fs').readFileSync(f, 'utf8')); console.log('json ok')"
  • rtk npx release-please --help

Notes

  • Release Please local debug mode could not run in this checkout because it tries to checkout main, which is already checked out by the existing .worktrees/windows-build-smoke worktree.
  • RELEASE_PLEASE_TOKEN must be configured before merging, otherwise the release-please workflow will fail on main.

@coderabbitai

coderabbitai Bot commented May 20, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@archae0pteryx has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 18 minutes and 56 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 5e1bc7b8-bc0a-4a6e-9e8d-d8af5bf4788a

📥 Commits

Reviewing files that changed from the base of the PR and between 9a7552c and 75f0203.

📒 Files selected for processing (4)
  • .github/workflows/release-please.yml
  • .release-please-manifest.json
  • README.md
  • release-please-config.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/release-please

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 and usage tips.

@archae0pteryx archae0pteryx merged commit 89a58bf into main May 20, 2026
2 checks passed
@archae0pteryx archae0pteryx deleted the feat/release-please branch May 20, 2026 22:25
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