chore(tak-cli): release v0.0.11 - #100
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe package version changes from 0.0.10 to 0.0.11. The changelog adds the 0.0.11 release entry with native CLI completions and dependency updates. ChangesRelease metadata
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Merge Risk: ⚪ Minimal · up to The release metadata update has no identified merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. Comment |
|
2245dd9 to
8c03266
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
Instruction counts
No instruction-count regression above 1%. Only instruction counts gate. Wall clock is shown for context — on identical hardware it moves 4-20% run to run. Measured by tak — instruction-counted CLI benchmarks, stored in this repository's git notes.
|
c327ceb to
83d55bc
Compare
133dbab to
08ed9c2
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
08ed9c2 to
7a29b62
Compare
7a29b62 to
f769595
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
f769595 to
192b68a
Compare
192b68a to
4ac8b56
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
e0a2da7 to
dd79f25
Compare
dd79f25 to
c9c2015
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
c9c2015 to
7e37a9e
Compare
03e79f1 to
4a9767a
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
9810bc7 to
325c9df
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
50c92ec to
3b78e41
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
3b78e41 to
277c627
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
277c627 to
89ac4fb
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
89ac4fb to
eabf170
Compare
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
The release PR was never merged automatically. `auto-merge-release.yml` looked for an open PR whose title starts with `chore: release`. But when release-plz releases a single crate, it titles the PR with the crate as a scope, for example `chore(tak-cli): release v0.0.12` (#133) or `chore(tak-cli): release v0.0.11` (#100). Neither the daily schedule nor a manual `gh workflow run auto-merge-release.yml` (the early-release path in RELEASING.md) found them. On 2026-09-24, run [36034389411](https://github.com/jdx/tak/actions/runs/36034389411) logged `No open release-plz release PR to main`, and #133 had to be merged by hand. ## Changes - **`auto-merge-release.yml`**: the title filter is now `test("^chore(\\([^)]+\\))?: release( |$)")`. It accepts both `chore(<crate>): release v<version>` and the unscoped `chore: release` that release-plz uses when it releases several crates at once (#27). The other checks are unchanged: head branch prefix `release-plz-`, head owner `jdx`, base `main`, and a non-empty body. - **`cliff.toml`**: the rule that keeps release commits out of the changelog now matches the same optional scope and requires a space or end of subject after `release`, like the PR-title filter (`^chore(\([^)]+\))?: (release|Release)( |$)`). A commit such as `chore(ci): release-plz config` therefore still appears in the changelog. ## Verification - I ran the new jq filter against every PR in the repo. It selects all past release PRs (#14 through #133, including #27's `chore: release`). - It rejects near-misses such as `chore: release-plz config`, `chore(ci): releases cleanup` and `fix: release foo`. *AI-assisted — Tool: Claude Code; model: anthropic/claude-opus-5-5; version: unavailable.* 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > CI and changelog regex tweaks only; no runtime or auth behavior changes. > > **Overview** > Fixes **release auto-merge** failing when release-plz opens a single-crate PR titled `chore(<crate>): release v<version>` instead of the unscoped `chore: release`. > > The **`auto-merge-release.yml`** jq title filter now uses a regex that accepts an optional scope before `release`, while keeping the existing guards (branch prefix, head owner, non-empty body). **`cliff.toml`** uses the same pattern so scoped release commits stay excluded from the changelog. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 4a6b591. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
🤖 New release
tak-cli: 0.0.10 -> 0.0.11 (⚠ API breaking changes)⚠
tak-clibreaking changesChangelog
This PR was generated with release-plz.
Note
Medium Risk
Version-only PR, but the published crate carries semver-breaking API removal (
Bench::argv) and bundles benchmark/runner behavior changes from the listed features.Overview
Release v0.0.11 for
tak-cli: bumps the crate version inCargo.toml/Cargo.lockand adds the 0.0.11 section toCHANGELOG.md(generated by git-cliff).The changelog captures work already merged since 0.0.10—not new logic in this diff—including interleaved, shuffled multi-command comparisons in
run, shell completions shipped in the packslip, Entire trail runners, and tooling/dependency maintenance (e.g. mr-boxington,usage-rs, mise.lock v2). Release notes flag an API break for Rust consumers: the publicBench::argvmethod is gone (command argv handling moved to internalCmd).Reviewed by Cursor Bugbot for commit eabf170. Bugbot is set up for automated code reviews on this repo. Configure here.