build(deps): bump insta from 1.40.0 to 1.41.0

[dependabot]

Bumps insta from 1.40.0 to 1.41.0.

Release notes

Sourced from insta's releases.

1.41.0

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

• --force-update-snapshots now causes cargo-insta to write every snapshot, regardless of whether snapshots fully match, and now implies --accept. This allows for --force-update-snapshots to update inline snapshots' delimiters and indentation.

  For the previous behavior of --force-update-snapshots, which limited writes to snapshots which didn't fully match, use --require-full-match. The main difference between --require-full-match and the existing behavior of --force-update-snapshots is a non-zero exit code on any snapshots which don't fully match.

  Like the previous behavior or --force-update-snapshots, --require-full-match doesn't track inline snapshots' delimiters or indentation, so can't update if those don't match. #644

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

• Warnings for undiscovered snapshots are more robust, and include files with custom snapshot extensions. #637

• Insta runs correctly on packages which reference rust files in a parent path. #626

• Warnings are printed when any snapshot uses a legacy format. #599

• cargo insta --version now prints a version. #665

• insta now internally uses INSTA_UPDATE=force rather than 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.

Changelog

Sourced from insta's changelog.

1.41.0

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

• --force-update-snapshots now causes cargo-insta to write every snapshot, regardless of whether snapshots fully match, and now implies --accept. This allows for --force-update-snapshots to update inline snapshots' delimiters and indentation.

  For the previous behavior of --force-update-snapshots, which limited writes to snapshots which didn't fully match, use --require-full-match. The main difference between --require-full-match and the existing behavior of --force-update-snapshots is a non-zero exit code on any snapshots which don't fully match.

  Like the previous behavior or --force-update-snapshots, --require-full-match doesn't track inline snapshots' delimiters or indentation, so can't update if those don't match. #644

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

• Warnings for undiscovered snapshots are more robust, and include files with custom snapshot extensions. #637

• Insta runs correctly on packages which reference rust files in a parent path. #626

• Warnings are printed when any snapshot uses a legacy format. #599

• cargo insta --version now prints a version. #665

• insta now internally uses INSTA_UPDATE=force rather than 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.

Commits

• 0317928 Refine changelog (#675)
• 0e07a50 Update a couple docstrings (#669)
• 083ce14 Another small simplification of prepare_test_runner (#667)
• b7dea9b Small simplification of prepare_test_runner (#666)
• 5fd34e6 Print a version with --version (#665)
• a8b6cc2 Small refactors (#664)
• 4f16d70 Show hidden files in functional tests (#663)
• 2b8fce7 Consolidate Cargo.toml creation in functional tests (#662)
• 10db5b0 Changelog refinements (#649)
• 6a37645 Better error message if cargo metadata fails (#661)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.