Skip to content

Update Rust crate insta to v1.43.1 #263

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 5, 2025

This PR contains the following updates:

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

Release Notes

mitsuhiko/insta (insta)

v1.43.1

Compare Source

This release in identical in rust code to 1.43.0, but reruns the GitHub Actions
workflows, which failed to create a release within GitHub for 1.43.0.

v1.43.0

Compare Source

  • Add uppercase keyboard shortcuts for bulk operations in cargo insta review:
    A to accept all, R to reject all, and S to skip all remaining snapshots.
    #​745
  • --unreferenced=auto (or other relevant values) no longer cleans up pending
    snapshots. A bug where cargo insta test --unreferenced=auto would
    incorrectly pass on new pending snapshots has been fixed.
  • Support specifying cargo-nextest bin with INSTA_CARGO_NEXTEST_BIN. #​721 (Louis Fruleux)
  • Allow setting INSTA_WORKSPACE_ROOT at compile time. This is useful for reproducible binaries
    so they don't contain references to CARGO_MANIFEST_DIR. #​726 (Pascal Bach)
  • Qualify all references in macros to avoid name clashes. #​729 (Austin Schey)
  • Remove linked-hash-map and pin-project dependencies. #​742, #​741, #​738
  • cargo insta review fails with a helpful error message when run in a non-TTY environment.

v1.42.2

Compare Source

  • Support other indention characters than spaces in inline snapshots. #​679
  • Fix an issue where multiple targets with the same root would cause too many pending snapshots to be reported. #​730
  • Hide unseen option in CLI, as it's pending deprecation. #​732
  • Stop \t and \x1b (ANSI color escape) from causing snapshots to be escaped. #​715
  • Improved handling of inline snapshots within allow_duplicates! { .. }. #​712

v1.42.1

Compare Source

  • Improved handling of control characters in inline snapshots. #​713
  • Add pending deprecation warning for --accept-unseen. We've left an issue
    open at #​659 eliciting feedback on
    whether anyone uses this for a few months. A warning will now be printed when
    --accept-unseen is used, and we'll eventually remove the feature unless we
    get some feedback that it's useful. #​668

v1.42.0

Compare Source

  • Text snapshots no longer contain snapshot_type: text in their metadata. For
    context, we originally added this in the prior release (1.41.0) to support
    binary snapshots, but some folks disliked the diff noise on any snapshot
    changes, and the maintainers' weighted votes favored reverting. I apologize
    that this will cause some additional churn for those who used cargo insta test --force-update-snapshots to update their snapshots to the 1.41 format;
    running this again with 1.42 will remove those metadata entries. To confirm:
    this doesn't affect whether snapshot tests pass or fail — the worst impact is
    some additional diffs in metadata. #​690
  • Pending snapshots are no longer removed throughout the workspace by
    cargo-insta before running tests. Instead, running a test will overwrite or
    remove its own pending snapshot. To remove all pending snapshots, use cargo insta reject or run tests with --unreferenced=delete. #​651
  • insta::internals::SettingsBindDropGuard (returned from
    Settings::bind_to_scope) no longer implements Send. This was incorrect and
    any tests relying on this behavior where not working properly. Fixes #​694 in
    #​695 by @​jalil-salame

Configuration

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

🚦 Automerge: Enabled.

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 force-pushed the renovate/insta-1.x-lockfile branch from 480284b to 76df48e Compare January 26, 2025 09:50
@renovate renovate bot changed the title Update Rust crate insta to v1.42.0 Update Rust crate insta to v1.42.1 Jan 26, 2025
@renovate renovate bot force-pushed the renovate/insta-1.x-lockfile branch from 76df48e to 7e0cba2 Compare March 2, 2025 02:22
@renovate renovate bot changed the title Update Rust crate insta to v1.42.1 Update Rust crate insta to v1.42.2 Mar 2, 2025
@renovate renovate bot force-pushed the renovate/insta-1.x-lockfile branch from 7e0cba2 to 5544fcc Compare April 25, 2025 23:34
@renovate renovate bot changed the title Update Rust crate insta to v1.42.2 Update Rust crate insta to v1.43.0 Apr 25, 2025
@renovate renovate bot force-pushed the renovate/insta-1.x-lockfile branch from 5544fcc to 3020877 Compare April 29, 2025 19:28
@renovate renovate bot changed the title Update Rust crate insta to v1.43.0 Update Rust crate insta to v1.43.1 Apr 29, 2025
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.

0 participants