chadtmiller.com/knotless

Switch repository

Loading…

What changes

knotless 0.11.0, as knope release --override-version 0.11.0 makes it from the four change files on main: the workspace version from 0.10.0 to 0.11.0 in Cargo.toml and the six crates' Cargo.lock entries, the version's CHANGELOG.md section, and the change files removed. One line of the section is edited by hand, to say knotless queue list where the change file said knotless queue.

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

Why

Stacked pulls are on main and on prod, but 0.10.0 and older clients fail on a pull that has moved off a landed pull, with has no branch <old base>. This ships the client that can act on one.

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

client.minimum stays as it is. It is set only when a release is found to harm repositories, and an older client refusing a moved pull harms none.

How it was checked

All six workspace crates' lock entries move to 0.11.0, and none names another at 0.10.0. The build is left to CI.

Changeset: none

Shortcomings

An older client still fails on a moved pull until it upgrades.

🤖 Generated with Claude Code

This is a mechanical release: the workspace version goes from 0.10.0 to 0.11.0, and the six workspace crates' Cargo.lock entries move with it. The four change files are removed. CHANGELOG.md gets a 0.11.0 section with the two minor changes under Features and the two patch changes under Fixes. The one hand edit, knotless queue list, matches the real command name.

I searched the repository for remaining 0.10.0 strings. The three left in Cargo.lock (lines 1179, 1554 and 3483) are not workspace crates, and the others are test fixtures and npm engine ranges. I did not build it, as the body says CI does that.

The 0.11.0 choice over knope's 0.10.1 is explained in the body, and I have no objection to it.