~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.13.0 Latest 2 packages, 1 image

1
10

Release 0.12.0

Merged
Merged chadtmiller.com asked to merge into main from chadtmiller.com/knotless:release/0.12.0

What changes

knotless 0.12.0, as knope release --override-version 0.12.0 makes it from the fourteen change files on main: the workspace version from 0.11.0 to 0.12.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.12.0 of the knotless package, and tags the commit v0.12.0.

Why

Main has seven features since 0.11.0 that live in the client or knotless-mcp: MCP resources, pull merge --auto, release yank, the Cargo registry, the queue off until a branch's rule turns it on, the review agent's rounds, and merge-when-checks-pass on the pages, with seven fixes. Users get the client side of them only from a release.

knope alone would make this 0.11.1, as it bumps a 0.x minor change as a patch. It is 0.12.0 for the new features, as 0.11.0 was.

client.minimum stays as it is: nothing here harms repositories when run by an older client.

How it was checked

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

Changeset: none

Approved

This is the 0.12.0 release bump. It changes the workspace version in Cargo.toml and the six workspace crates' Cargo.lock entries. It adds the 0.12.0 CHANGELOG section and removes the fourteen change files. I checked three things, and all hold:

  • The fourteen deleted files in .changeset/ match the fourteen files the base branch has there.
  • The CHANGELOG section reproduces each change file's heading and text. It puts the six minor changes under Features and the eight patch changes under Fixes.
  • The only other 0.11.0 left in Cargo.lock is pulldown-cmark-escape, which is a third-party crate and should stay.

I did not build anything or read the CI runs; the build is left to CI, as the body says. The Changeset: none line fits, because the pull changes no source under crates/knotless*/src. The 0.12.0 choice over knope's 0.11.1 is explained in the body.

Merged as f9fe46c