chadtmiller.com/knotless

Switch repository

Loading…

What changes

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

knope.toml now names knotless-agent among the Cargo.lock entries it bumps. That crate came after the list was written, so knope left its lock entry at 0.2.0, and cargo clippy --locked refused the lock.

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.3.0 of the knotless package, then tags the commit v0.3.0. The deploy publishes its image as 0.3.0 of knotless-server. It becomes the latest, so install.sh serves it.

Why

A release of what has landed since 0.2.0: archived repositories, owner secrets sealed to runners, a read-only knotless-mcp and the review agent, partial edits and ranged reads, repository topics, notifications of one kind and of failed checks, update checks, and the fixes in the changelog.

knope alone would make it 0.2.1, since before 1.0 it turns a minor change into a patch bump. As with 0.2.0, the 14 features read better as a minor version, so it is set by hand.

How it was checked

knope release --override-version 0.3.0. cargo metadata --locked --offline passes on the fixed lock. Only the version lines in Cargo.toml and Cargo.lock change, besides the changelog and the removed change files. The build is left to CI.

Shortcomings

A published version can't be taken back.

🤖 Generated with Claude Code

This is a mechanical 0.3.0 release. The workspace version moves from 0.2.0 to 0.3.0 in Cargo.toml, and the five workspace crates in Cargo.lock move with it. The 23 change files are removed, and each one has a matching entry in the new CHANGELOG.md section: 14 features and 9 fixes. I found nothing that needs changing. I did not check CI or the release workflows. One small thing in the description: it says 13 features, but the changelog lists 14. The changelog is correct.

The new commit fixes the stale lock entry. knotless-agent in Cargo.lock moves from 0.2.0 to 0.3.0, and knope.toml now lists it among the lock entries knope bumps, so the next release won't leave it behind. That was the only change since my last review, which asked for nothing. I did not check CI or the release workflows.