chore(deps): update rust crate insta to v1#11
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
a2d00be to
8ec6626
Compare
8ec6626 to
1283ba9
Compare
1283ba9 to
7c8a1be
Compare
7c8a1be to
f7489c3
Compare
f7489c3 to
f1f55d0
Compare
f1f55d0 to
c3a15d4
Compare
537e09f to
8d3cf1d
Compare
8d3cf1d to
bed37d1
Compare
bed37d1 to
3564ebc
Compare
3564ebc to
d4508a6
Compare
d4508a6 to
67b5467
Compare
67b5467 to
14b55b4
Compare
14b55b4 to
45c108b
Compare
45c108b to
df527ce
Compare
c01fb23 to
827b01c
Compare
8ae7077 to
60bba2d
Compare
60bba2d to
b9dbb3e
Compare
b9dbb3e to
3235b6e
Compare
3235b6e to
8b48f0c
Compare
0501d56 to
60c1e1b
Compare
60c1e1b to
cf8ff6b
Compare
cf8ff6b to
06d8851
Compare
06d8851 to
721019b
Compare
aba2d85 to
24943ce
Compare
24943ce to
e641de4
Compare
add4f86 to
f758714
Compare
f758714 to
264c9bd
Compare
264c9bd to
36c3be0
Compare
36c3be0 to
3cb3fef
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.16→1.0Release Notes
mitsuhiko/insta (insta)
v1.46.3Compare Source
v1.46.2Compare Source
leading_space()function incorrectly treated\ras indentation, causing carriage returns to be stripped from snapshot content. #866< 0.4.17upper bound on globset dependency. #864v1.46.1Compare Source
with_settings!macro. #858v1.46.0Compare Source
INSTA_PENDING_DIRenvironment variable for Bazel and other hermetic build systems. When set, pending snapshots are written to a separate directory while keeping the source tree read-only. We are very open to feedback on this feature. #852test.runner_fallbackconfig key. #853v1.45.1Compare Source
v1.45.0Compare Source
INSTA_DIFF_TOOLenvironment variable. When set, insta uses the specified tool (e.g.,delta,difftastic) to display snapshot diffs instead of the built-in diff. The tool is invoked as<tool> <old_file> <new_file>. #844test.disable_nextest_doctestconfig option toinsta.yaml, allowing users to silence the nextest doctest warning via config instead of passing--dndevery time. #842--unreferenced=rejectwithout false positives on.snapfiles from other tools. #846clippy::needless_raw_stringslint by only using raw strings when content contains backslashes or quotes. #828v1.44.3Compare Source
======or similar patterns as conflicts. #832let output = assert_snapshot!(...)). #833v1.44.2Compare Source
NEXTEST_RUN_IDenvironment variable. #824v1.44.1Compare Source
--dndalias for--disable-nextest-doctestflag to make it easier to silence the deprecation warning. #822v1.44.0Compare Source
(LLMs, CI pipelines, scripts).
cargo insta review --snapshot <path>andcargo insta reject --snapshot <path>now work without a terminal. Enhancedpending-snapshotsoutput with usage instructions and workspace-relative paths. #815--disable-nextest-doctestflag tocargo insta testto disable running doctests withnextest. Shows a deprecation warning when nextest is used with doctests without this flag, to prepare
cargo instato no longer runa separate doctest process when using nextest in the future. #803
--test-runner-fallback/--no-test-runner-fallbackflags tocargo insta test. #811the 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 stillcurrently allow differing trailing newlines, though may adjust this in the
future). #563
v1.43.2Compare Source
cargo metadatafails to execute or parse (e.g., when cargo is not in PATH or returns invalid output). Now falls back to using the manifest directory as the workspace root. #798 (@adriangb)uninlined_format_argslint warnings. #801INSTA_GLOB_FILTER. #786libccrate to0.2.174, fixing building on musl targets, and increasing the MSRV ofinstato1.64.0(released Sept 2022). #784v1.43.1Compare 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.0Compare Source
cargo insta review:Ato accept all,Rto reject all, andSto skip all remaining snapshots.#745
--unreferenced=auto(or other relevant values) no longer cleans up pendingsnapshots. A bug where
cargo insta test --unreferenced=autowouldincorrectly pass on new pending snapshots has been fixed.
cargo-nextestbin withINSTA_CARGO_NEXTEST_BIN. #721 (Louis Fruleux)INSTA_WORKSPACE_ROOTat compile time. This is useful for reproducible binariesso they don't contain references to
CARGO_MANIFEST_DIR. #726 (Pascal Bach)linked-hash-mapandpin-projectdependencies. #742, #741, #738cargo insta reviewfails with a helpful error message when run in a non-TTY environment.v1.42.2Compare Source
unseenoption in CLI, as it's pending deprecation. #732\tand\x1b(ANSI color escape) from causing snapshots to be escaped. #715allow_duplicates! { .. }. #712v1.42.1Compare Source
--accept-unseen. We've left an issueopen at #659 eliciting feedback on
whether anyone uses this for a few months. A warning will now be printed when
--accept-unseenis used, and we'll eventually remove the feature unless weget some feedback that it's useful. #668
v1.42.0Compare Source
snapshot_type: textin their metadata. Forcontext, 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-snapshotsto 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
cargo-instabefore running tests. Instead, running a test will overwrite orremove its own pending snapshot. To remove all pending snapshots, use
cargo insta rejector run tests with--unreferenced=delete. #651insta::internals::SettingsBindDropGuard(returned fromSettings::bind_to_scope) no longer implementsSend. This was incorrect andany tests relying on this behavior where not working properly. Fixes #694 in
#695 by @jalil-salame
v1.41.1Compare Source
v1.41.0Compare Source
Experimental support for binary snapshots. #610 (Florian Plattner)
--force-update-snapshotsnow causescargo-instato write every snapshot, regardless of whethersnapshots fully match, and now implies
--accept. Thisallows for
--force-update-snapshotsto update inline snapshots'delimiters and indentation.
For the previous behavior of
--force-update-snapshots, which limited writes tosnapshots which didn't fully match, use
--require-full-match.The main difference between
--require-full-matchand the existing behavior of--force-update-snapshotsis a non-zero exit code on any snapshots which don't fully match.
Like the previous behavior of
--force-update-snapshots,--require-full-matchdoesn'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. #603Warnings 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 --versionnow prints a version. #665instanow internally usesINSTA_UPDATE=forcerather thanINSTA_FORCE_UPDATE=1. (This doesn't affect users ofcargo-insta, whichhandles 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.v1.40.0Compare Source
cargo-instano longer panics when runningcargo insta test --accept --workspaceon a workspace with a default crate. #532
MSRV for
instahas been raised to 1.60, and forcargo-instato 1.64.Added support for compact debug snapshots (
assert_compact_debug_snapshot). #514Deprecate
--no-force-passincargo-insta. The--checkoption covers thesame functionality and has a clearer name. #513
Inline snapshots now use the required number of
#s to escape the snapshotvalue, rather than always using
###. This allows snapshotting values whichthemselves contain
###. If there are no existing#characters in thesnapshot value, a single
#will be used. #540Inline snapshots can now be updated with
--force-update-snapshots. #569cargo insta testaccepts multiple--excludeflags. #520testrunnerin insta's yaml config works. #544Print a warning when encountering old snapshot formats. #503
Group the options in
cargo insta --help, upgrade toclapfromstructopt. #518No longer suggest running
cargo instamessage when runningcargo insta test --check. #515Print a clearer error message when accepting a snapshot that was removed. #516
Mark
require-full-matchas experimental, given some corner-cases are currently difficult to manage. #497Add a new integration test approach for
cargo-instaand a set of integration tests. #537Enable Filters to be created from
IntoIteratortypes, rather than justVecs. #570Implemented total sort order for an internal
Keytype correctly. This prevents potentialcrashes introduced by the new sort algorithm in Rust 1.81. #586
v1.39.0Compare Source
Fixed a bug in
require_full_match. #485Fixed a bug that caused snapshot and module names to sometimes be inaccurate. #483
Insta will no longer error when attempting to remove snapshots that were already removed. #484
Added support for trailing commas in inline snapshots. #472
Don't pass
--colorin all cases tolibtestany more to work around limitationswith custom test harnesses. #491
v1.38.0Compare Source
Filtersis now constructible fromIntoIterator. #400Change
stdmacro calls to be fully qualified. This fixes issues wherethe prelude was not used or the macros were overridden. #469
v1.37.0Compare Source
All macros for file snapshots should now handle trailing commas (but not yet inline snapshots)
Vendored old
yaml-rustdependency to avoid rustsec warnings. #465v1.36.1Compare Source
v1.36.0Compare Source
Deprecate
INSTA_FORCE_UPDATE_SNAPSHOTSenv-var forINSTA_FORCE_UPDATE.The latter was documented, the former was implemented. #449
Add
require_full_matchoption. #448Deprecate
assert_display_snapshot!. #385v1.35.1Compare Source
v1.35.0Compare Source
.configwas in the root.match .. { ... }syntax to redactions for betterrustfmtsupport. (#428)--packageparameter can be supplied multiple times now. (#427)inline snapshots that were never able to match. (#444)
cargo insta testnow accepts the--testparameter multiple times. (#437)v1.34.0Compare Source
cargo-instainto a workspace. (#410)--manifest-pathwith regards to virtual workspaces. (#409)v1.33.0Compare Source
--all-targetsparameter support tocargo insta test. (#408)v1.32.0Compare Source
--profileparameter support tocargo insta test.v1.31.0Compare Source
cargo insta testnot to report test failures.needless_raw_string_hashesclippy lint on inline snapshots. (#390)v1.30.0Compare Source
input_filenot to be written into thesnapshots. (#386)
--accepteven if a test outsideinsta fails. (#358)
#[must_use].--color=...to libtest to propagate color choices in more situations. (#375)v1.29.0Compare Source
rendered to the terminal width).
--excludeoption tocargo insta test. (#360)coloroption from aCARGO_TERM_COLORenvironment variable (#361)v1.28.0Compare Source
allow_duplicates!to enable multiple assertions for asingle snapshot. (#346)
rustfmtuse unix newlines.glob!to set a different basepath. (#347)
rounded_redactionto truncate floating point values. (#350)v1.26.0Compare Source
glob!optional to better support WASI.v1.24.1Compare Source
--include-hiddenflag (#331)review.include_ignored(#330)v1.24.0Compare Source
.config/insta.yaml) to change thebehavior of insta and cargo-insta. (#322)
--no-ignoreto--include-ignored.--include-hiddento instruct insta to also walk intohidden paths.
--unreferencedoption tocargo-insta testwhich allowsfine tuning of what should happen with unreferenced files. It's now
possible to ignore (default), warn, reject or delete unreferenced
snapshots. (#328)
test targeting. (#317)
v1.23.0Compare Source
v1.22.0Compare Source
should make sure that ANSI sequences in strings are no longer screwing
up the terminal output. (#308)
--targetoption tocargo insta test. (#309)suffixes. This allows patterns such as
foo/*/*.txtwithoutcreating conflicts. (#310)
v1.21.2Compare Source
cargo insta test. (#305)v1.21.1cargo insta test.v1.21.0cargo insta showcommand to render a snapshot.v1.20.0Compare Source
cargo instanow supports nextest as test runner. (#285)glob!macro now defers failures by default. (#284)v1.19.1Compare Source
v1.19.0Compare Source
backtracefeature.serializationfeature.assert_json_snapshot!andassert_yaml_snapshot!now requirethe
jsonandyamlfeature respectively.not supported (#272)
INSTA_GLOB_FILTERto skip over tests expandedfrom a glob. (#274)
v1.18.2Compare Source
#[allow(unused)]in the macro. (#271)v1.18.1Compare Source
tuple variants. (#270)
v1.18.0Settings::bindnow can return a result.bind_to_scope.serdedependency is now optional. While still enabled by defaultusers need to opt into
yamlandjsonfeatures explicitly to regainsupport for it. To avoid the default
serdedependency the defaultfeatures just need to be disabled. (#255)
serializationfeatures.backtracefeature.Settings::bind_to_thread.Breaking Changes / Upgrading: If you are upgrading to serde 1.18.0 you will
receive deprecating warnings if you are using the
assert_yaml_snapshot!andassert_json_snapshot!macros. These macros will continue to function in thefuture but they will require explicit opting into the
yamlandjsonfeatures.To silence the warning add them to your
instadependency. Additionally thebacktracefeature was deprecated. It is no longer needed so just remove it.v1.17.2v1.17.1work. (#252)
v1.17.0cargo-instawhere sometimes accepting inline snapshotswould crash with an out of bounds panic.
filtersfeature. (#245)with_settings!macro now inherits the former settings rather than resetting. (#249)Settings::bind_to_scopeand deprecatedSettings::bind_to_thread. (#250)minimal-versionsbuilds.v1.16.0Compare Source
--no-quiet/-Qflag tocargo insta testto suppress thequiet flag. This works around limitations with custom test harnesses
such as cucumber.
with_settings!. It's now a perfect match tothe settings object's setter methods.
descriptionandinfoto snapshots. (#239)omit_expressionsetting. (#239)v1.15.0Compare Source
serde-yaml dependency no longer supports older versions of Rust.
v1.14.1Compare Source
"foo\n". (#225)v1.14.0Compare Source
moved since the time of the snapshot creation. (#220)
cargo insta testnow returns non zero status code when snapshotsare left for review. (#222)
cargo insta test. (#223)v1.13.0assertion_lineis no longer retained in snapshots. (#218)v1.12.0sorted_redactionandSettings::sort_selector). (#212)Upgrade Notes:
Insta used to detect the current test name by using the current thread name. This
appeared to work well but unfortunately ran into various limitations. In particular
in some cases the thread name was truncated, missing or did not point to the current
test name. To better support different platforms and situations insta now uses the
function name instead.
This however changes behavior. In particular if you are using a helper function to
assert, a different snapshot name will now be used. You can work around this issue
by using a helper macro instead or to explicitly pass a snapshot name in such
situations.
v1.11.0Compare Source
once_cell. (#208)v1.10.0Compare Source
v1.9.0Compare Source
cargo-instanow correctly handles the package (-p) argumenton
testwhen deleting unreferenced snapshots. (#201)v1.8.0Compare Source
will quickly be old, they are often useful when reviewing snapshots
immediately after creation with
cargo-insta. (#191)v1.7.2Compare Source
cargo test. (#183)Box::leak. (#185)INSTA_WORKSPACE_ROOTis set, the value is used as the manifestdirectory rather than whatever
CARGO_MANIFEST_DIRwas set to at compiletime. (#180)
v1.7.1Compare Source
v1.7.0Compare Source
v1.6.3Compare Source
v1.6.2Compare Source
v1.6.1Compare Source
v1.6.0Compare Source
multiple rows. (#156)
v1.5.3similar.
v1.5.2v1.5.1Compare Source
v1.5.0Compare Source
pending-snapshotsparameter tocargo-insta.cargo-instanow honors ignore files. This can be overriddenwith
--no-ignore.cargo-instanow supports the vscode extension.v1.4.0Compare Source
--delete-unreferenced-snapshotsparameter tocargo-insta.globsetcrate for theglobfeature.INSTA_UPDATEis set toalwaysorunseenit won'tfail on execution.
v1.3.0Compare Source
Content.v1.2.0Compare Source
v1.1.0Compare Source
INSTA_SNAPSHOT_REFERENCES_FILEenvironment variable to supportdeletions of unreferenced snapshot files. (#136)
prepend_module_to_snapshotflag to disable prepending of modulenames to snapshot files. (#133)
consoledependency optional. Thecolorsfeature can be disabled nowwhich disables colored output.
v1.0.0Compare Source
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.
This PR was generated by Mend Renovate. View the repository job log.