chore: release cargo-anvil 0.7.0 and cargo-aprz 1.1.2 - #156
Merged
Conversation
Prepared with `scripts/release-crate.ps1`. cargo-anvil 0.6.0 -> 0.7.0 (minor: the range since the `cargo-anvil-v0.6.0` tag carries a feature). `.anvil.lock` is regenerated so its `tool_version` matches the new crate version and `regenerate-check` stays green. cargo-aprz 1.1.1 -> 1.1.2 and cargo-aprz-lib 1.1.1 -> 1.1.2 (patch). The binary crate itself is unchanged; the fix that needs republishing lives in cargo-aprz-lib, so both move together to keep the pair in lockstep and to give `cargo install cargo-aprz` a release that carries it. The HTML report snapshot embeds the crate version and is updated with it. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
The changes are consistent, self-contained release/version updates with corresponding changelog and regenerated version-stamped artifacts.
Pull request overview
Prepares crates.io releases for cargo-anvil (0.7.0) and cargo-aprz / cargo-aprz-lib (1.1.2) by applying coordinated version bumps and regenerating the few version-stamped artifacts required for a clean publish and anvil --dry-run drift checks.
Changes:
- Bump crate versions for
cargo-anvilto 0.7.0 andcargo-aprz/cargo-aprz-libto 1.1.2 (plus corresponding workspace/Cargo.lock updates). - Add release entries to the relevant changelogs for the new versions.
- Regenerate version-stamped artifacts (
.anvil.lock, the HTML report snapshot, andcargo-anvilREADME link refs).
File summaries
| File | Description |
|---|---|
| crates/cargo-aprz/CHANGELOG.md | Adds a 1.1.2 release note entry referencing the cargo-aprz-lib update. |
| crates/cargo-aprz/Cargo.toml | Bumps cargo-aprz package version to 1.1.2. |
| crates/cargo-aprz-lib/src/reports/snapshots/cargo_aprz_lib__reports__snapshot_tests__html_report.snap | Updates the embedded “Produced by cargo-aprz …” version string to 1.1.2. |
| crates/cargo-aprz-lib/CHANGELOG.md | Adds a 1.1.2 release note entry for dependency removals. |
| crates/cargo-aprz-lib/Cargo.toml | Bumps cargo-aprz-lib package version to 1.1.2. |
| crates/cargo-anvil/README.md | Updates docs.rs links / doc2readme metadata to reference 0.7.0. |
| crates/cargo-anvil/CHANGELOG.md | Adds a 0.7.0 release section with linked PRs. |
| crates/cargo-anvil/Cargo.toml | Bumps cargo-anvil package version to 0.7.0. |
| Cargo.toml | Updates workspace dependency version for cargo-aprz-lib to 1.1.2. |
| Cargo.lock | Updates locked versions for cargo-anvil, cargo-aprz, and cargo-aprz-lib. |
| .anvil.lock | Updates the recorded anvil tool version to 0.7.0. |
Review details
- Files reviewed: 9/11 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
martinhavelka (wukchung)
approved these changes
Sep 3, 2026
Evgenii (Vaiz)
enabled auto-merge (squash)
September 3, 2026 12:14
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #156 +/- ##
=======================================
- Coverage 97.6% 97.6% -0.1%
=======================================
Files 298 296 -2
Lines 67348 66349 -999
=======================================
- Hits 65761 64771 -990
+ Misses 1587 1578 -9 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Evgeny Fedorov (evgenyfedorov2)
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Clawpilot here! Posted automatically by Clawpilot (an AI agent), not by a human. Please verify before acting.
Prepares crates.io releases for
cargo-anvilandcargo-aprzin one PR. Everything was produced byscripts/release-crate.ps1, except the three follow-ups called out under Manual additions below.Versions
cargo-anvilcargo-anvil-v0.6.0tag contains a feature (#152), so a minor bump is the semver-correct step for a0.xcrate.cargo-aprz-libcargo-aprz-lib-v1.1.1.cargo-aprzWhy
cargo-aprz-libis in a PR that was asked to releasecargo-aprzcrates/cargo-aprzhas zero commits since itscargo-aprz-v1.1.1tag — the binary is a thin shell overcargo-aprz-lib, and the fix worth republishing (#145, dropping thedirectoriesandhumantime-serdedependencies) lives entirely in the library. Releasing the binary without the library would publish nothing new, so both move to 1.1.2 together. That also keeps the pair in lockstep, which is how they have been versioned so far.Changelogs
Both generated sections come from the commit range since each crate's own release tag. Note that
cargo-anvil-v0.6.0andcargo-aprz-lib-v1.1.1both point at2937b1b, not at the commits that bumped the versions, so several anvil-touching commits that look unreleased ingit logwere in fact already inside the published 0.6.0 tarball and are correctly absent here.Manual additions on top of the script
.anvil.lock— regenerated withcargo run -p cargo-anvil -- anvil. The lockfile recordstool_version, so bumping the crate to 0.7.0 without regenerating would have failed theregenerate-checkjob.cargo anvil --dry-runis now clean.crates/cargo-aprz-lib/src/reports/snapshots/…__html_report.snap— the HTML report embeds the producing crate version (Produced by cargo-aprz 1.1.2). The previous version bump, chore: Bump versions so these tools get republished from this repo #132, had to do the same.crates/cargo-aprz/CHANGELOG.md— the script emitted nothing, because no commit touched that directory. A one-line entry was added by hand so the crate does not ship a version with no release notes; without itpublish-gh-release.rsfalls back to the bare stringRelease cargo-aprz v1.1.2.Validation
cargo check --workspace --all-targets --locked— passes, soCargo.lockis consistent with the new versionscargo test -p cargo-anvil— 409 + 100 tests passcargo test -p cargo-aprz-lib --lib reports::snapshot_tests— 10 passcargo run -p cargo-anvil -- anvil --dry-run— no driftjust anvil-spellcheck— cleanNote, not fixed here
crates/cargo-aprz-lib/CHANGELOG.mdstill carries a stale## [Unreleased]heading that now sits below the new 1.1.2 section. It dates back to the crate's import in #76 and describes work that shipped in 1.1.1, so relabelling it would assert a release date this PR cannot verify. Left alone deliberately; it does not affect release-note extraction, which stops at the next##heading.