chadtmiller.com/knotless

Switch repository

Loading…

What changes

knotless 0.10.0, as knope release --override-version 0.10.0 makes it from the three change files on main: the workspace version from 0.9.0 to 0.10.0 in Cargo.toml and the six crates' Cargo.lock entries, the version's CHANGELOG.md section, and the change files removed.

Once this lands and main's checks pass at it, release.yml builds the client for every target, publishes it as release 0.10.0 of the knotless package, and tags the commit v0.10.0.

Why

Main's AGENTS.md and the docs already name the grouped commands (knotless pull create, knotless run rerun), and the hosted MCP tools are renamed, but no published client has those commands. This ships them, with knotless run cancel and sites for private repositories.

knope alone would make this 0.9.1, as it bumps a 0.x minor change as a patch. It is 0.10.0 for the new features, as 0.9.0 was.

client.minimum stays at 0.6.0. It is set only when a release is found to harm repositories, and nothing since 0.9.0 fixes such harm. Older clients keep working, and they say a newer release is out.

How it was checked

All six workspace crates' lock entries move to 0.10.0, and none names another at 0.9.0. The old names are covered by old_names_still_work (crates/knotless/tests/cli.rs) and the tests in oldnames.rs. The build is left to CI.

Changeset: none

Shortcomings

The old names work for this release. A later pull removes oldnames.rs, once prod's host and the shared steps run the grouped commands.

🤖 Generated with Claude Code

This is a mechanical release of 0.10.0. It bumps the workspace version in Cargo.toml, moves the six workspace crates' Cargo.lock entries to 0.10.0, and adds the 0.10.0 section to CHANGELOG.md. It deletes the three change files, and their text matches the new changelog entries. The remaining 0.9.0 hits are the old changelog heading, a test fixture in release.rs and third-party lock entries. I couldn't confirm the third-party attribution for the three Cargo.lock hits, since the search shows only the version lines. None of them is a workspace crate. I didn't build or run the tests; the PR body leaves the build to CI. Keeping client.minimum at 0.6.0 is reasonable for the reason the body gives.