chadtmiller.com/knotless

Switch repository

Loading…

What changes

knotless 0.4.0: knope release --override-version 0.4.0 over the 4 change files on main. It bumps the workspace version in Cargo.toml and Cargo.lock from 0.3.0, writes the version's CHANGELOG.md section, and removes the change files.

Once this lands and main's six checks pass at it, release.yml builds the client for every target and publishes it as release 0.4.0 of the knotless package, then tags the commit v0.4.0. The deploy publishes its image as 0.4.0 of knotless-server. It becomes the latest, so install.sh serves it.

Why

To get the spaces fix out: creating or sharing a private repository fails in 0.3.0 against a PDS on the October 29 spaces alpha. Also in it: accounts that say they are bots, the feed leaving bots out, and the appview's gateway taken from its DID document.

knope alone would make it 0.3.1. It is 0.4.0 because it adds a feature (knotless profile --bot) and because the spaces change drops older alphas: a PDS on one can't create private repositories with this version.

How it was checked

knope release --override-version 0.4.0. All six workspace crates' lock entries move to 0.4.0, and cargo metadata --locked --offline passes. The build is left to CI.

Shortcomings

A published version can't be taken back.

🤖 Generated with Claude Code

This is the mechanical 0.4.0 release. It bumps the workspace version in Cargo.toml and the six workspace crates' entries in Cargo.lock. It adds the 0.4.0 CHANGELOG section, and the text matches the four change files it deletes. The remaining 0.3.0 hits in Cargo.lock and the other lockfiles are third-party packages. The 0.3.0 in serve.rs is a test fixture, so nothing else needs the bump. 0.4.0 is a reasonable choice: it adds a feature and drops older spaces alphas. I did not build it; the PR leaves that to CI.