Affected crate(s)
cargo-soothfast
Version
0.3.2
Steps to reproduce
- Have a repo with at least one release tag and a populated Unreleased section, e.g.
## Unreleased (draft vs v3.0.0) with ### ✨ Features / ### 📦 Dependencies / ### 🔧 Internal entry lists under it.
- Run
report changelog without --against-ref:
cargo soothfast report changelog -p <pkg> --baseline base --features full
- Read
CHANGELOG.md.
In CI the flag is rarely omitted on purpose — it is omitted by accident. action/regen.sh passes it only when prev=$(git describe --tags --abbrev=0) is non-empty, and that depends on tags having been fetched. action/prepare.sh:33-34 unshallows with --tags only if [ "$(git rev-parse --is-shallow-repository)" = true ]. A job checked out at fetch-depth: 0 is not shallow, so that branch never runs, and actions/checkout passes --no-tags with fetch-tags defaulting to false. Any job that regenerates the changelog from a full-depth checkout therefore silently takes the no-tag path.
Expected behavior
Either the entries are preserved, or the command says out loud that it is about to replace a populated Unreleased section with one containing no commit entries — the way changelog_already_cut already prints when it declines to regenerate.
An initial-surface changelog is a legitimate mode for a genuine first release. The problem is that it is indistinguishable, from the command's output, from total accidental content loss.
Actual behavior
The Unreleased section is silently replaced with ## Unreleased (initial public surface) and zero commit entries. merge_changelog writes that over the real section. Nothing in stdout indicates anything was dropped; the command prints its usual report: regenerated CHANGELOG.md and exits 0.
In cargo-soothfast/src/report.rs at v0.3.2, against_ref: None takes four separate branches, three of which drop content:
:265 changelog_already_cut(&existing, None) — loses the tag comparison its own rustdoc (:403) describes as the thing that makes it discriminate.:281 → ApiSection::Initial(&entries) instead of the diff.:300 → ref_baseline = None, so the perf section becomes a point-in-time snapshot.:308 → changes = Vec::new(). This is the one that empties the section; merged_changes is never called at all.
Rust version
rustc 1.98.0 (88d9e12ae 2026-08-18)
Operating system
CachyOS (Linux 7.2.3), and GitHub Actions ubuntu-latest
Measurement backend (soothfast-measure issues only)
Not applicable
Affected crate(s)
cargo-soothfast
Version
0.3.2
Steps to reproduce
## Unreleased (draft vs v3.0.0)with### ✨ Features/### 📦 Dependencies/### 🔧 Internalentry lists under it.report changelogwithout--against-ref:CHANGELOG.md.In CI the flag is rarely omitted on purpose — it is omitted by accident.
action/regen.shpasses it only whenprev=$(git describe --tags --abbrev=0)is non-empty, and that depends on tags having been fetched.action/prepare.sh:33-34unshallows with--tagsonlyif [ "$(git rev-parse --is-shallow-repository)" = true ]. A job checked out atfetch-depth: 0is not shallow, so that branch never runs, andactions/checkoutpasses--no-tagswithfetch-tagsdefaulting to false. Any job that regenerates the changelog from a full-depth checkout therefore silently takes the no-tag path.Expected behavior
Either the entries are preserved, or the command says out loud that it is about to replace a populated Unreleased section with one containing no commit entries — the way
changelog_already_cutalready prints when it declines to regenerate.An initial-surface changelog is a legitimate mode for a genuine first release. The problem is that it is indistinguishable, from the command's output, from total accidental content loss.
Actual behavior
The Unreleased section is silently replaced with
## Unreleased (initial public surface)and zero commit entries.merge_changelogwrites that over the real section. Nothing in stdout indicates anything was dropped; the command prints its usualreport: regenerated CHANGELOG.mdand exits 0.In
cargo-soothfast/src/report.rsat v0.3.2,against_ref: Nonetakes four separate branches, three of which drop content::265changelog_already_cut(&existing, None)— loses the tag comparison its own rustdoc (:403) describes as the thing that makes it discriminate.:281→ApiSection::Initial(&entries)instead of the diff.:300→ref_baseline = None, so the perf section becomes a point-in-time snapshot.:308→changes = Vec::new(). This is the one that empties the section;merged_changesis never called at all.Rust version
rustc 1.98.0 (88d9e12ae 2026-08-18)
Operating system
CachyOS (Linux 7.2.3), and GitHub Actions ubuntu-latest
Measurement backend (soothfast-measure issues only)
Not applicable