Skip to content

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Nov 20, 2025

This PR contains the following updates:

Package Update Change
cargo-insta minor 1.43.2 -> 1.44.3

Release Notes

mitsuhiko/insta (cargo-insta)

v1.44.3

Compare Source

  • Fix a regression in 1.44.2 where merge conflict detection was too aggressive, incorrectly flagging snapshot content containing ====== or similar patterns as conflicts. #​832
  • Fix a regression in 1.42.2 where inline snapshot updates would corrupt the file when code preceded the macro (e.g., let output = assert_snapshot!(...)). #​833

v1.44.2

Compare Source

  • Fix a rare backward compatibility issue where inline snapshots using an uncommon legacy format (single-line content stored in multiline raw strings) could fail to match after 1.44.0. #​830
  • Handle merge conflicts in snapshot files gracefully. When a snapshot file contains git merge conflict markers, insta now detects them and treats the snapshot as missing, allowing tests to continue and create a new pending snapshot for review. #​829
  • Skip nextest_doctest tests when cargo-nextest is not installed. #​826
  • Fix functional tests failing under nextest due to inherited NEXTEST_RUN_ID environment variable. #​824

v1.44.1

Compare Source

  • Add --dnd alias for --disable-nextest-doctest flag to make it easier to silence the deprecation warning. #​822
  • Update cargo-dist to 0.30.2 and fix Windows runner to use windows-2022. #​821

v1.44.0

Compare Source

  • Added non-interactive snapshot review and reject modes for use in non-TTY environments
    (LLMs, CI pipelines, scripts). cargo insta review --snapshot <path> and
    cargo insta reject --snapshot <path> now work without a terminal. Enhanced
    pending-snapshots output with usage instructions and workspace-relative paths. #​815
  • Add --disable-nextest-doctest flag to cargo insta test to disable running doctests with
    nextest. Shows a deprecation warning when nextest is used with doctests without this flag, to prepare cargo insta to no longer run
    a separate doctest process when using nextest in the future. #​803
  • Add ergonomic --test-runner-fallback / --no-test-runner-fallback flags to cargo insta test. #​811
  • Apply redactions to snapshot metadata. #​813
  • Remove confusing 'previously unseen snapshot' message. #​812
  • Speed up JSON float rendering. #​806 (@​nyurik)
  • Allow globset version up to 0.4.16. #​810 (@​g0hl1n)
  • Improve documentation. #​814 (@​tshepang)
  • We no longer trim starting newlines during assertions, which allows asserting
    the number of leading newlines match. Existing assertions with different
    leading newlines will pass and print a warning suggesting running with
    --force-update-snapshots. They may fail in the future. (Note that we still
    currently allow differing trailing newlines, though may adjust this in the
    future). #​563

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot changed the title Update dependency cargo-insta to v1.44.1 Update dependency cargo-insta to v1.44.2 Nov 27, 2025
@renovate-bot renovate-bot force-pushed the renovate/cargo-insta-1.x branch from 827a396 to 9696a28 Compare November 27, 2025 11:13
@renovate-bot renovate-bot changed the title Update dependency cargo-insta to v1.44.2 Update dependency cargo-insta to v1.44.3 Nov 28, 2025
@renovate-bot renovate-bot force-pushed the renovate/cargo-insta-1.x branch from 9696a28 to d90c0b7 Compare November 28, 2025 00:49
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