chadtmiller.com/knotless

Switch repository

Loading…

What changes

knotless 0.6.0 is knope release --override-version 0.6.0 run over the 19 change files on main. It bumps the workspace version from 0.5.0 to 0.6.0 in Cargo.toml and Cargo.lock, writes the version's CHANGELOG.md section, and removes the change files.

Once this lands and main's checks pass at it, release.yml builds the client for every target and publishes it as release 0.6.0 of the knotless package, then tags the commit v0.6.0. It becomes the latest release, so install.sh serves it.

Why

Deleting a branch now deletes its ref record, and a new ref starts at a generation taken from the clock. An older client that makes a branch again under a recently deleted name can have its pushes refused. So prod's KNOTLESS_CLIENT_MINIMUM is to be raised to 0.6.0 once it is out, and that needs a release that holds the change.

It also brings the rest of what has landed since 0.5.0:

• knotless admin logs;
• workflows on a schedule;
• watching repositories and subscribing to threads;
• organization admins managing settings and secrets;
• private records named by their space URI;
• shared steps given secrets under the names they ask for;
• reading refs side by side;
• and the queue and checks fixes.

knope alone would make this 0.5.1, since it bumps a 0.x minor change as a patch. It is 0.6.0 because of the new features, and because it changes how refs are stored.

How it was checked

knope release --override-version 0.6.0: all six workspace crates' lock entries move to 0.6.0. The build is left to CI.

Changeset: none

Shortcomings

A published version can't be taken back.

🤖 Generated with Claude Code

This is a mechanical release commit. It bumps the workspace version to 0.6.0 in Cargo.toml and in the six workspace crates' Cargo.lock entries. It adds the 0.6.0 section to CHANGELOG.md and deletes the change files.

The 19 deleted .changeset/*.md files match the 19 changelog entries, and their text is carried over unchanged. Features and fixes are grouped by each file's minor or patch bump. A search of the default branch for 0.5.0 finds only the old changelog heading and third-party packages, so no other workspace version is left behind. The only Cargo.lock lines changed are the six workspace crates' versions.

Choosing 0.6.0 over knope's 0.5.1 is reasonable, since it carries new features and the ref-storage change, and the changelog says to upgrade every pushing client. The build is left to CI, as the body says, so wait for main's checks before the release workflow publishes. I did not look at the checks.