Skip to content

chore: release v0.4.0 - #43

Merged
newhoggy merged 1 commit into
mainfrom
release-plz-2026-10-07T15-25-01Z
Oct 9, 2026
Merged

newhoggy merged 1 commit into
mainfrom
release-plz-2026-10-07T15-25-01Z

Conversation

@newhoggy

@newhoggy newhoggy commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

🤖 New release

  • patchcov: 0.3.0 -> 0.4.0 (⚠ API breaking changes)

⚠ patchcov breaking changes

--- failure constructible_struct_adds_field: struct exhaustively constructible through public API adds field ---

Description:
A pub struct that could be exhaustively constructed with a literal using only public API has a new pub field, breaking existing exhaustive literals.
        ref: https://doc.rust-lang.org/reference/expressions/struct-expr.html
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/constructible_struct_adds_field.ron

Failed in:
  field Cli.error_format in /tmp/.tmpLCNaX2/patchcov/src/cli.rs:57
Changelog

0.4.0 - 2026-10-09

Added

  • (cli) mark a truncated path-mismatch sample and name its size once
  • (cli) JSON lines for lint-markers findings and the merge summary
  • (cli) structured fields on JSON warnings
  • (cli) structured gate fields in the JSON error output
  • (cli) print warnings as JSON lines under --error-format json
  • (cli) opt-in JSON error output on stderr
  • [breaking] exit with a distinct code for each class of failure
  • (diff) [breaking] fail by default when a report's paths match no tracked file
  • (diff) detect the default base branch from origin/HEAD, main or master

Documentation

  • align path-mismatch example with checkout normalization
  • (reference) explain the path-mismatch change when upgrading from 0.3.0
  • (reference) show level in the gate error example
  • (reference) show the anchored report path in the JSON warning examples
  • (troubleshooting) say a path mismatch exits 7, not 1
  • (reference) word the path-mismatch truncation rule without Rust notation
  • (reference) say how to tell that a path-mismatch unmatched sample is truncated
  • (cli) tighten the note on display-string paths in JSON warnings
  • (cli) say the report and shard fields of JSON warnings are display strings
  • (reference) describe the JSON finding and merge summary lines
  • (reference) list the fields of each JSON warning kind
  • recommend cargo install --locked and document the fresh-resolution MSRV job
  • (reference) document the JSON warning line and the error level
  • (readme) say the other formats fail under --branch-coverage
  • (readme) say which report formats support --branch-coverage in the intro
  • (reference) document the exit code for each failure class
  • (release) anchor the docs changelog parser and list every group
  • (release) group docs commits under Documentation in the changelog
  • describe the default base branch resolution order
  • (contributing) clarify what CI covers for lint-markers and docs
  • (readme) address review of the mission and branch-coverage wording
  • (readme) add a mission statement and fix the branch-coverage line

Fixed

  • (cli) discover diff repositories from subdirectories
  • (cli) preserve input arguments in report and shard labels
  • (cli) explain spaced negative float thresholds
  • (cli) preserve chain and gates in JSON error fallback
  • (cli) simplify the mismatch-sample suffix and tighten docs wording
  • (cli) address review of the JSON error fallback
  • (cli) keep code in the JSON error line when the full report cannot be serialized
  • (tests) match GitHub more closely in the doc link check
  • (cli) report a missing --fail-under-* value instead of blaming the next argument
  • (cli) carry the record's level and kind into the JSON fallback line
  • (cli) print a minimal JSON line when a record fails to serialize
  • (diff) normalise -0 thresholds and cover negatives end to end
  • (diff) reject negative --fail-under-patch and --fail-under-lines values
  • (markers) make MarkerError non-exhaustive and tidy the JSON line docs
  • (cli) reject non-finite --fail-under-patch / --fail-under-lines values
  • (cli) report measured gate values unrounded
  • (ci) run the real unlocked cargo install in the fresh-resolution job
  • (cli) address review of the JSON warnings
  • (cli) address review of the JSON error output
  • (cli) address review of the exit-code change
  • (diff) keep the deprecated --fail-on-path-mismatch a pure no-op
  • (diff) name the chosen base in the merge-base error; isolate the master test

Other

Changed

  • Report and shard diagnostic labels now preserve the input argument in diff and
    merge, even with -C. This changes warning messages and JSON report/shard
    values that previously included the working directory, and the corresponding
    path-mismatch and empty-shard error messages. File resolution is unchanged.


This PR was generated with release-plz.

@newhoggy
newhoggy force-pushed the release-plz-2026-10-07T15-25-01Z branch 4 times, most recently from 47faa8c to 5edffd9 Compare October 7, 2026 15:40
@newhoggy newhoggy changed the title chore: release v0.3.1 chore: release v0.4.0 Oct 7, 2026
@newhoggy
newhoggy force-pushed the release-plz-2026-10-07T15-25-01Z branch 25 times, most recently from f34bd58 to 30ce843 Compare October 9, 2026 01:39
@newhoggy
newhoggy force-pushed the release-plz-2026-10-07T15-25-01Z branch 18 times, most recently from 56c2ffb to 521596a Compare October 9, 2026 06:09
@newhoggy
newhoggy force-pushed the release-plz-2026-10-07T15-25-01Z branch from 521596a to 903a95f Compare October 9, 2026 06:26
@newhoggy
newhoggy added this pull request to the merge queue Oct 9, 2026
Merged via the queue into main with commit d0ebccc Oct 9, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant