chadtmiller.com/knotless

Switch repository

Loading…

What changes

knotless 0.9.0, as knope release --override-version 0.9.0 makes it from the four change files on main: the workspace version from 0.8.0 to 0.9.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.9.0 of the knotless package, and tags the commit v0.9.0.

Why

It ships knotless site, so that anyone can deploy a repository's site to knotless.page now that it is served, and the site shared step (chadtmiller.com/steps/site@1) has a client to run. It also brings the merge queue's keeper, refs naming their packs, and a review refusal that no longer tells an author to approve their own pull.

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

How it was checked

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

Changeset: none

🤖 Generated with Claude Code

This is the 0.9.0 release commit. It bumps the workspace version in Cargo.toml and the six workspace crates' Cargo.lock entries (knotless, -agent, -mcp, -run, -serve, -triage). It adds the 0.9.0 CHANGELOG.md section and deletes the four change files.

Every piece checks out:

• The changelog entries match the deleted change files word for word. They are sorted into Features (keeper, sites) and Fixes (own-pull approval, refs naming packs).
• The only remaining 0.8.0 strings in Cargo.lock are heapless and poly1305, which are external crates and correctly untouched.
• The body explains why this is 0.9.0 and not knope's 0.8.1. It also carries Changeset: none, which fits a release commit that changes no client source.

I didn't build it. The body leaves the build to CI, and the repository says CI does the building.