Release sq
Maintainer checklist for preparing an `sq` release in this repository up to tag creation/push. Use when bumping `sq`, validating the crate release, drafting notes, or preparing a tag before the manual GitHub Release publish step.From its SKILL.md
npx -y skills add DerekStride/sq --skill release-sqAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.4 KB, as published. Nobody here has run it
Release sq
Use this skill when preparing a new sq release for this repository.
sq is published as the sift-queue crate from the repository root.
Source of truth
Release automation lives in:
.github/workflows/publish.yml
Key behavior:
- pushing a
v*tag runs a version check - publishing a GitHub Release triggers
cargo publish - the tag version must match
Cargo.toml
Example for v0.3.0:
- git tag:
v0.3.0 - crate version:
0.3.0
Maintainer checklist
- DO NOT create the github release
- DO NOT publish the crate yourself
This skill documents the prep work up to tag creation/push. The GitHub Release publication and post-publish verification are handled manually afterward.
-
Bump the version in
Cargo.toml,package.json, and.claude-plugin/marketplace.json. -
Update the
sq --versionassertions intests/cli_integration.rs. -
Run the Rust test suite:
cargo test --all --verbose -
Run a crates.io dry run:
cargo publish --dry-run -
Draft release notes in
tmp/release-vX.Y.Z.md. -
Commit the release prep, merge to
main, then create and push the tag:git tag vX.Y.Z git push origin main vX.Y.Z
Version update locations
Update every release-owned version reference:
Cargo.toml— crate version and source of truthCargo.lock—sift-queuepackage version; regenerated by Cargo after changingCargo.tomlpackage.json— Pi/OMP package version; must matchCargo.toml.claude-plugin/marketplace.json— Claude plugin marketplace version; must matchCargo.tomltests/cli_integration.rs— expected output for bothsq --versionandsq -vtmp/release-vX.Y.Z.md— filename, heading, and changelog comparison URL for the new release
Also create and push the matching vX.Y.Z Git tag. .github/workflows/publish.yml derives artifact and Homebrew versions from that tag; it contains no release number to edit.
Notes
- Tag format must be
vX.Y.Z, not justX.Y.Z. - Tag push alone does not publish the crate.
- Actual crates.io publication happens only after the GitHub Release is published.