Skip to content

chore(deps): update rust crate insta to v1.41.1 #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2024

This PR contains the following updates:

Package Type Update Change
insta (source) dev-dependencies minor 1.40.0 -> 1.41.1

Release Notes

mitsuhiko/insta (insta)

v1.41.1

Compare Source

  • Re-release of 1.41.1 to generate release artifacts correctly.

v1.41.0

Compare Source

  • 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 of --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.


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 is behind base branch, 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 renovate bot changed the title chore(deps): update rust crate insta to v1.41.0 chore(deps): update rust crate insta to v1.41.1 Oct 31, 2024
@renovate renovate bot force-pushed the renovate/insta-1.x-lockfile branch from 842a34a to 14e7b77 Compare October 31, 2024 20:34
@DeveloperC286 DeveloperC286 merged commit b6b7037 into main Nov 12, 2024
10 of 11 checks passed
@DeveloperC286 DeveloperC286 deleted the renovate/insta-1.x-lockfile branch November 12, 2024 10:15
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