chadtmiller.com/knotless

Switch repository

Loading…

What changes

knotless 0.5.0: knope release --override-version 0.5.0 over the 8 change files on main. It bumps the workspace version in Cargo.toml and Cargo.lock from 0.4.0, 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.5.0 of the knotless package, then tags the commit v0.5.0. The deploy publishes its image as 0.5.0 of knotless-server. It becomes the latest, so install.sh serves it.

Why

Shared steps are live on the runners and listed on the pages at /steps, but no released CLI has knotless uses update, so nobody can pin a step without building from source. Also in it:

• steps that run only at some refs (on);
• logins and gateway grants that name knotless's own space types instead of every app's spaces;
• an organization's space type of its own, so 0.4.0's org join --hidden stops writing into the old space;
• show listing the pulls that mention an issue;
• themes of your own;
• status showing the server's disk;
• ejected pulls' logs.

knope alone would make it 0.4.1, since it bumps a 0.x minor change as a patch. It is 0.5.0 because it adds features (uses, step on, themes) and changes what a login asks for.

How it was checked

knope release --override-version 0.5.0. All six workspace crates' lock entries move to 0.5.0, and cargo metadata --locked --offline passes. The build is left to CI. This is also release.yml's first real release since it moved onto the shared wait-for-checks step.

Shortcomings

A published version can't be taken back.

🤖 Generated with Claude Code

This is the mechanical 0.5.0 release. It bumps the workspace version in Cargo.toml to 0.5.0. It moves the six workspace crates' entries in Cargo.lock from 0.4.0 to 0.5.0. It adds a 0.5.0 section to CHANGELOG.md and deletes the 8 change files. The changelog entries match the deleted change files word for word. Features and fixes are sorted by their minor and patch levels. I found nothing that must change.

I did not build it, and the pull says CI does that. The 0.5.0 override is justified in the body: the minor changes include new features and a changed login scope. I did not check that CI passes at this commit.