chore(cargo-anvil): release v0.9.0

[st-dev-gh]

[copilot speaking]

Summary

Release cargo-anvil 0.9.0 from the complete set of cargo-anvil changes merged since the 0.8.0 tag, repair the missing 0.8.0 changelog history, and add a reproducible changelog-backfill mode to the release script.

cargo-anvil 0.9.0

The generated 0.9.0 changelog contains every commit touching the crate since cargo-anvil-v0.8.0:

Bug fixes

• retry oversized Windows coverage exports (fix(cargo-anvil): retry oversized Windows coverage exports #166)
• make anvil-fmt run the pinned nightly rustfmt (fix(cargo-anvil): make anvil-fmt actually run the pinned nightly rustfmt #159)
• address validation follow-ups (fix(cargo-anvil): address validation follow-ups #131)
• remove Bash from generated ADO steps (fix(cargo-anvil): remove Bash from ADO steps #160)

Performance

• parallelize Miri test artifacts (perf(cargo-anvil): parallelize Miri test artifacts #123)

Build system

• bump the cargo-coverage-gate and cargo-heather catalog pins (build(anvil): bump cargo-coverage-gate and cargo-heather catalog pins #167)

The crate manifest, workspace lockfile, generated crate README, and .anvil.lock metadata are updated for 0.9.0. Applying cargo-anvil records tool_version = "0.9.0" while preserving the catalog checksum generated by current main.

Reconstructed 0.8.0 history

The cargo-anvil-v0.8.0 tag existed without a corresponding changelog section. This PR reconstructs that section from the authoritative range:

cargo-anvil-v0.7.0..cargo-anvil-v0.8.0

The section records the breaking ADO stage-identification change (#154), the aggregate CI gate (#158), and container-based MSRV resolution (#155).

Changelog backfill support

release-crate.ps1 now supports:

.\scripts\release-crate.ps1 <crate> -BackfillVersion <version>

Backfill mode:

• requires an existing target release tag and preceding semantic-version tag
• derives the commit range from those tags
• reuses Conventional Commit grouping and PR-link formatting
• inserts or replaces the version section in semantic-version order
• changes only the crate changelog
• produces stable output when repeated
• rejects combination with -Version or -Bump

The normal release path also no longer fabricates an “Initial release” section when an established changelog contains a historical gap.

Validation

• cargo-anvil dry-run reports no generated repository drift
• formatting and spelling checks pass
• crate READMEs were regenerated
• repeated backfill produces identical output
• invalid tags and conflicting release options are rejected

[Copilot]

🟢 Approval recommended

The changes are consistent with a release PR (version/lock/README regeneration) and the new -BackfillVersion mode is implemented with clear validation and bounded behavior.

Pull request overview

This PR prepares the cargo-anvil v0.9.0 release by updating crate/version artifacts, regenerating generated docs, and enhancing the release automation script to support reconstructing missing changelog entries from existing git tags.

Changes:

• Add an idempotent -BackfillVersion mode to scripts/release-crate.ps1 to reconstruct an already-tagged version’s changelog section from the previous semver tag through the target tag.
• Regenerate crates/cargo-anvil/CHANGELOG.md (including backfilled 0.8.0) and refresh generated README link/version metadata for 0.9.0.
• Bump cargo-anvil to 0.9.0 and update Cargo.lock accordingly.

File summaries

File	Description
scripts/release-crate.ps1	Adds -BackfillVersion flow and improves changelog “initial release” detection behavior when there are version gaps.
README.md	Documents how to use -BackfillVersion to reconstruct a missing changelog section for a tagged release.
crates/cargo-anvil/README.md	Regenerated README metadata/links to point at 0.9.0 docs.
crates/cargo-anvil/CHANGELOG.md	Adds Unreleased, records 0.9.0, and includes reconstructed 0.8.0 section.
crates/cargo-anvil/Cargo.toml	Bumps crate version from 0.8.0 to 0.9.0.
Cargo.lock	Updates the locked cargo-anvil package version to 0.9.0.

Review details

• Files reviewed: 5/6 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Codecov Comments Bot (codecov-commenter)]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.5%. Comparing base (26e5c60) to head (8edc524).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #164     +/-   ##
=======================================
- Coverage   97.5%   97.5%   -0.1%     
=======================================
  Files        300     300             
  Lines      68538   68538             
=======================================
- Hits       66876   66873      -3     
- Misses      1662    1665      +3     

Flag	Coverage Δ
linux	97.5% <ø> (ø)
linux-arm	97.5% <ø> (+<0.1%)	⬆️
scheduled	?
windows	97.7% <ø> (+<0.1%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

🟢 Approval recommended

The changes are consistent with the stated release goals, and the new backfill workflow is clearly validated, isolated, and documented.

Review details

• Files reviewed: 5/7 changed files
• Comments generated: 0 new
• Review effort level: Lite

[Evgenii (Vaiz)]

st-dev-gh, could we merge #159 & #162 first?

[martintmk]

And also this one:

#166

(blocks our oxidizer PRs)

[Evgenii (Vaiz)]

and #167 :D

[Evgenii (Vaiz)]

you can ignore #162

[st-dev-gh]

st-dev-gh, could we merge #159 & #162 first?

Let's include #159.

#162 is draft again and I think it can wait for another release-train if needed.

[Evgenii (Vaiz)]

#159 has been merged

[Copilot]

🔵 Needs a closer look

It modifies the release script and multiple release-critical artifacts (versions, lockfiles, changelog, and generated documentation), which warrants final human verification before merging.

Review details

• Files reviewed: 5/7 changed files
• Comments generated: 0 new
• Review effort level: Lite