Skip to content

Commit

Permalink
Changelog refinements (#649)
Browse files Browse the repository at this point in the history
  • Loading branch information
max-sixty authored Oct 12, 2024
1 parent 6a37645 commit 10db5b0
Showing 1 changed file with 12 additions and 8 deletions.
20 changes: 12 additions & 8 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,16 +6,17 @@ All notable changes to insta and cargo-insta are documented here.

- Experimental support for binary snapshots. #610 (Florian Plattner)

- `--force-update-snapshots` now writes every snapshot, regardless of whether
`insta` evaluates a write is required, and now implies `--accept`. This
- `--force-update-snapshots` now causes `cargo-insta` to write every snapshot, regardless of whether
it evaluates snapshots fully match, and now implies `--accept`. This
allows for `--force-update-snapshots` to update inline snapshots when
delimiters or indents require updating.
delimiters or indentation can be updated.

For the existing behavior of limiting writes which `insta` can evaluate are
required, use `--require-full-match`. The main difference between
For the existing behavior of limiting writes to when `insta` evaluates writes
are required, use `--require-full-match`. The main difference between
`--require-full-match` and the existing behavior of `--force-update-snapshots`
is that the test run will return a non-zero exit code if any snapshots don't
match fully. #644
is that `cargo-insta` will return a non-zero exit code if any snapshots don't
match fully. `--require-full-match` doesn't track inline snapshots' delimiters or
indentation. #644

- Inline snapshots only use `#` characters as delimiters when required. #603

Expand All @@ -27,9 +28,12 @@ All notable changes to insta and cargo-insta are documented here.
- Warnings are printed when any snapshot uses a legacy format. #599

- `insta` now internally uses `INSTA_UPDATE=force` rather than
`INSTA_FORCE_UPDATE`. (This doesn't affect users of `cargo-insta`, which
`INSTA_FORCE_UPDATE=1`. (This doesn't affect users of `cargo-insta`, which
handles this internally.) #482

- `cargo-insta`'s integration tests continue to grow over the past couple of versions,
and now offer coverage of most of `cargo-insta`'s interface.

## 1.40.0

- `cargo-insta` no longer panics when running `cargo insta test --accept --workspace`
Expand Down

0 comments on commit 10db5b0

Please sign in to comment.