Bump the minor-updates group with 3 updates

[dependabot]

Bumps the minor-updates group with 3 updates: regex, anyhow and insta.

Updates regex from 1.11.0 to 1.11.1

Changelog

Sourced from regex's changelog.

1.11.1 (2024-10-24)

This is a new patch release of regex that fixes compilation on nightly Rust when the unstable pattern crate feature is enabled. Users on nightly Rust without this feature enabled are unaffected.

Bug fixes:

• [BUG #1231](rust-lang/regex#1231): Fix the Pattern trait implementation as a result of nightly API breakage.

Commits

• 9870c06 1.11.1
• 80df54e changelog: 1.11.1
• 991ba88 unstable: fix Pattern trait implementation
• See full diff in compare view

Updates anyhow from 1.0.90 to 1.0.91

Release notes

Sourced from anyhow's releases.

1.0.91

• Ensure OUT_DIR is left with deterministic contents after build script execution (#388)

Commits

• 6c52daa Release 1.0.91
• 4986853 Merge pull request #388 from dtolnay/outdir
• f130b76 Clean up dep-info files from OUT_DIR
• See full diff in compare view

Updates 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.