Skip to content

chore(tak-cli): release v0.0.11 - #100

Merged
jdx merged 1 commit into
mainfrom
release-plz-2026-09-05T23-48-52Z
Sep 24, 2026
Merged

jdx merged 1 commit into
mainfrom
release-plz-2026-09-05T23-48-52Z

Conversation

@jdx

@jdx jdx commented Sep 5, 2026 •

Copy link
Copy Markdown
Owner

🤖 New release

  • tak-cli: 0.0.10 -> 0.0.11 (⚠ API breaking changes)

⚠ tak-cli breaking changes

--- failure inherent_method_missing: pub method removed or renamed ---

Description:
A publicly-visible method or associated fn is no longer available under its prior name. It may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.50.0/src/lints/inherent_method_missing.ron

Failed in:
  Bench::argv, previously in file /tmp/.tmpksJFWZ/tak-cli/src/config.rs:60
Changelog

0.0.11 - 2026-09-24

🚀 Features

  • (cli) publish native completions in packslip by @jdx in #99
  • (run) compare several commands with interleaved, shuffled samples by @jdx in #131

🛡️ Security

  • add entire trail runners by @jdx in #116

🔍 Other Changes

  • float jdx tools on latest without a release-age delay by @jdx in #130

📦️ Dependency Updates


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 in Cargo.toml / Cargo.lock and adds the 0.0.11 section to CHANGELOG.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 public Bench::argv method is gone (command argv handling moved to internal Cmd).

Reviewed by Cursor Bugbot for commit eabf170. Bugbot is set up for automated code reviews on this repo. Configure here.

@coderabbitai

coderabbitai Bot commented Sep 5, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

Note

Reviews paused

It 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 reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: 193e28fe-16e3-44d8-99fe-23cb45e0fe84

📥 Commits

Reviewing files that changed from the base of the PR and between f769595 and 192b68a.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • CHANGELOG.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The 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.

Changes

Release metadata

Layer / File(s) Summary
Version and changelog update
Cargo.toml, CHANGELOG.md
tak-cli changes to version 0.0.11. The changelog records native CLI completions and dependency updates.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 192b6

The release metadata update has no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the package and the primary change: releasing version 0.0.11.

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.

@greptile-apps

greptile-apps Bot commented Sep 5, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

The release metadata changes appear safe to merge.

Summary

Updates tak-cli for the v0.0.11 release.

  • Bumps the package version from 0.0.10 to 0.0.11 in the manifest and lockfile.
  • Adds the generated v0.0.11 changelog entry covering features, security work, and dependency updates.

Reviews (34) · Last reviewed commit: "chore(tak-cli): release v0.0.11"

greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 5, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 2245dd9 to 8c03266 Compare September 6, 2026 00:48
@greptile-apps
greptile-apps Bot dismissed their stale review September 6, 2026 00:48

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

@github-actions

github-actions Bot commented Sep 6, 2026 •

Copy link
Copy Markdown

Instruction counts

benchmark trend instructions Δ wall (min) Δ
help ▁█ 647,420 → 647,590 +0.03% 0.97 → 0.88ms -9.65%
version ▁█ 478,601 → 478,757 +0.03% 0.98 → 0.77ms -21.18%

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.

4a9767a7b5a5 vs 72ff4bcf0cf1 · measured on the runner, not pushed to the history.

@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch 2 times, most recently from c327ceb to 83d55bc Compare September 8, 2026 06:51
greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 8, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch 4 times, most recently from 133dbab to 08ed9c2 Compare September 10, 2026 02:08
@greptile-apps
greptile-apps Bot dismissed their stale review September 10, 2026 02:08

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 08ed9c2 to 7a29b62 Compare September 10, 2026 02:17
greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 10, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 7a29b62 to f769595 Compare September 11, 2026 19:01
@greptile-apps
greptile-apps Bot dismissed their stale review September 11, 2026 19:01

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from f769595 to 192b68a Compare September 14, 2026 05:19
greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 14, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 192b68a to 4ac8b56 Compare September 15, 2026 05:35
@greptile-apps
greptile-apps Bot dismissed their stale review September 15, 2026 05:35

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch 3 times, most recently from e0a2da7 to dd79f25 Compare September 16, 2026 00:48
greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 16, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from dd79f25 to c9c2015 Compare September 17, 2026 18:51
@greptile-apps
greptile-apps Bot dismissed their stale review September 17, 2026 18:51

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 17, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from c9c2015 to 7e37a9e Compare September 19, 2026 19:42
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 03e79f1 to 4a9767a Compare September 23, 2026 13:46
@greptile-apps
greptile-apps Bot dismissed their stale review September 23, 2026 13:46

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 23, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch 4 times, most recently from 9810bc7 to 325c9df Compare September 23, 2026 16:36
@greptile-apps
greptile-apps Bot dismissed their stale review September 23, 2026 16:36

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 23, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch 5 times, most recently from 50c92ec to 3b78e41 Compare September 23, 2026 18:53
@greptile-apps
greptile-apps Bot dismissed their stale review September 23, 2026 18:53

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 23, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 3b78e41 to 277c627 Compare September 23, 2026 19:11
@greptile-apps
greptile-apps Bot dismissed their stale review September 23, 2026 19:11

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 23, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 277c627 to 89ac4fb Compare September 23, 2026 19:31
@greptile-apps
greptile-apps Bot dismissed their stale review September 23, 2026 19:31

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Sep 23, 2026
@jdx
jdx force-pushed the release-plz-2026-09-05T23-48-52Z branch from 89ac4fb to eabf170 Compare September 24, 2026 14:53
@greptile-apps
greptile-apps Bot dismissed their stale review September 24, 2026 14:53

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

@jdx
jdx merged commit e139140 into main Sep 24, 2026
15 of 17 checks passed
@jdx
jdx deleted the release-plz-2026-09-05T23-48-52Z branch September 24, 2026 15:00
jdx added a commit that referenced this pull request Sep 24, 2026
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>
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