chore: release cargo-anvil 0.9.0 - #170
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The changelog currently includes a duplicate/conflicting 0.8.0 section that should be removed before release.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR performs the cargo-anvil 0.9.0 release update: bumping the crate version, regenerating the changelog content for 0.9.0 (and backfilling 0.8.0), and updating Anvil’s lock metadata to match.
Changes:
- Bump
cargo-anvilversion to 0.9.0 (and updateCargo.lockaccordingly). - Regenerate
crates/cargo-anvil/CHANGELOG.mdwith new0.9.0and0.8.0sections plus an[Unreleased]header. - Update
.anvil.lockto reflecttool_version = 0.9.0.
File summaries
| File | Description |
|---|---|
| crates/cargo-anvil/CHANGELOG.md | Adds 0.9.0 notes and backfills 0.8.0, but currently contains a duplicate 0.8.0 section at the end. |
| crates/cargo-anvil/Cargo.toml | Bumps cargo-anvil crate version to 0.9.0. |
| Cargo.lock | Updates the resolved cargo-anvil package version to 0.9.0. |
| .anvil.lock | Updates Anvil tool version metadata from 0.8.0 to 0.9.0. |
Review details
- Files reviewed: 2/4 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| ## [0.8.0] - 2026-09-04 | ||
|
|
||
| - Initial release. |
There was a problem hiding this comment.
🟡 Changes recommended
The changelog currently contains a duplicate 0.8.0 section (conflicting with the earlier 0.8.0 entry), which should be corrected before publishing release notes.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
crates/cargo-anvil/CHANGELOG.md:170
- The changelog contains two separate
## [0.8.0] - 2026-09-04sections (one near the top and another appended at the end). This makes the release history ambiguous and the trailing- Initial release.line conflicts with the detailed 0.8.0 entries above. Remove the duplicate trailing 0.8.0 section so 0.8.0 is defined exactly once.
## [0.8.0] - 2026-09-04
- Initial release.
- Files reviewed: 3/5 changed files
- Comments generated: 1
- Review effort level: Lite
| [__link25]: https://docs.rs/cargo-anvil/0.9.0/cargo_anvil/?search=Catalog::anvil | ||
| [__link26]: https://docs.rs/cargo-anvil/0.9.0/cargo_anvil/?search=Artifact | ||
| [__link27]: https://docs.rs/cargo-anvil/0.9.0/cargo_anvil/fn.run_app.html |
There was a problem hiding this comment.
Addressed in 261e00a. The README is now regenerated with cargo-doc2readme (pinned 0.7.3) rather than hand-edited — both the docs.rs links and the encoded [__cargo_doc2readme_dependencies_info] blob now reflect 0.9.0, and cargo doc2readme --lib --check reports Readme is up to date. The PR description has been updated to match (it no longer claims No crate README changes).
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (97.5%) is below the target coverage (100.0%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #170 +/- ##
=====================================
Coverage 97.5% 97.5%
=====================================
Files 300 300
Lines 68538 68538
=====================================
+ Hits 66876 66877 +1
+ Misses 1662 1661 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
18d2049 to
8229b93
Compare
There was a problem hiding this comment.
🔵 Needs a closer look
crates/cargo-anvil/CHANGELOG.md currently contains a duplicate/conflicting 0.8.0 section at the end, which makes the release notes inconsistent.
Review details
Suppressed comments (2)
crates/cargo-anvil/CHANGELOG.md:170
- The changelog now contains a second "## [0.8.0] - 2026-09-04" section at the end ("- Initial release."), which duplicates and contradicts the earlier 0.8.0 entry (lines 22-35). This will confuse consumers and makes the release notes inconsistent.
## [0.8.0] - 2026-09-04
- Initial release.
crates/cargo-anvil/README.md:422
- PR description says there are no crate README changes, but this diff updates docs.rs links and the doc2readme dependency-info footer to 0.9.0. Please either update the PR description to reflect the README regen or revert the README changes so the description and patch agree.
[__link25]: https://docs.rs/cargo-anvil/0.9.0/cargo_anvil/?search=Catalog::anvil
[__link26]: https://docs.rs/cargo-anvil/0.9.0/cargo_anvil/?search=Artifact
[__link27]: https://docs.rs/cargo-anvil/0.9.0/cargo_anvil/fn.run_app.html
- Files reviewed: 3/5 changed files
- Comments generated: 0 new
- Review effort level: Lite
Bump cargo-anvil 0.8.0 -> 0.9.0 and regenerate CHANGELOG.md via scripts/release-crate.ps1. On merge, automation tags the commit and publishes the crate to crates.io. This release carries #167 (catalog pins: cargo-coverage-gate 0.4.0, cargo-heather 0.3.0) plus the accumulated fixes/perf since 0.8.0. Also backfills the previously-missing [0.8.0] CHANGELOG section — 0.8.0 was tagged and published via #158 without a changelog entry — so the history is contiguous. Regenerated .anvil.lock (tool_version 0.8.0 -> 0.9.0). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 381c59e2-8fdb-4f43-b21e-2760b6dcb2da
Regenerate cargo-anvil's README with cargo-doc2readme so the version-embedded docs.rs intra-doc links and the encoded [__cargo_doc2readme_dependencies_info] blob both reflect the 0.9.0 release bump. The anvil-readme-check compares the blob's recorded dependency versions against the crate's current requirements, so a stale 0.8.0 blob failed the check with "Readme links to incompatible version of dependency cargo-anvil". Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 381c59e2-8fdb-4f43-b21e-2760b6dcb2da
8229b93 to
261e00a
Compare
There was a problem hiding this comment.
🟢 Approval recommended
The changes are consistent, release-scoped metadata/regeneration updates with no apparent inconsistencies in the updated artifacts.
Review details
- Files reviewed: 3/5 changed files
- Comments generated: 0 new
- Review effort level: Lite
|
Closing as a duplicate. 👍 martin-kolinek pointed out (in the Please Review thread) that this release was already handled by #164 ( So the goal of #170 — publishing 0.9.0 (carrying #167's |
What
Release cargo-anvil 0.9.0 — version bump + regenerated changelog via
scripts/release-crate.ps1. On merge, automation tags the commit and publishes the crate to crates.io.Why now
This is the release that carries #167 (catalog pins
cargo-coverage-gate0.4.0 /cargo-heather0.3.0) onto crates.io, so downstream consumers (e.g. the internal substrate flavor) can pick the new pins up by bumping theircargo-anvildependency. It also ships the accumulated fixes/perf since 0.8.0.Contents (
v0.8.0..HEAD)Also in this PR
[0.8.0]CHANGELOG section. 0.8.0 was tagged (cargo-anvil-v0.8.0) and published via feat(anvil): replace legacy CI with aggregate gate #158 without a changelog entry, leaving a gap between[0.9.0]and[0.7.0]. Restored it (breaking feat(cargo-anvil)!: identify the ADO stage on every job wrapper invocation #154, feat feat(anvil): replace legacy CI with aggregate gate #158, fix fix(cargo-anvil): let the container image resolve the declared MSRV #155) so the history is contiguous. Also dropped a stray duplicate[0.8.0] - Initial release.block thatrelease-crate.ps1appended at the end of the file, so there is now a single, correctly-ordered[0.8.0]section.crates/cargo-anvil/README.mdwithcargo-doc2readme(pinned 0.7.3) so the version-embedded docs.rs intra-doc links and the encoded[__cargo_doc2readme_dependencies_info]blob track the 0.9.0 bump — theanvil-readme-checkcompares that blob's recorded dependency versions against the crate's current requirements, so a stale 0.8.0 blob fails the check..anvil.lock(tool_version0.8.0 → 0.9.0) soregenerate-checkstays green.Validation
cargo test -p cargo-anvil— all green (415+ tests).cargo anvil --dry-run— clean (no generated-content or.anvil.lockdrift).cargo doc2readme --lib --check(incrates/cargo-anvil) —Readme is up to date.Notes: the
[Unreleased]header is emitted byrelease-crate.ps1.