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:
2.2.4
->2.2.5
1.40.0
->1.41.0
1.0.88
->1.0.89
1.0.210
->1.0.213
2.0.82
->2.0.85
1.0.64
->1.0.65
Release Notes
mitsuhiko/insta (insta)
v1.41.0
Compare Source
Experimental support for binary snapshots. #610 (Florian Plattner)
--force-update-snapshots
now causescargo-insta
to write every snapshot, regardless of whethersnapshots fully match, and now implies
--accept
. Thisallows for
--force-update-snapshots
to 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-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. #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 --version
now prints a version. #665insta
now internally usesINSTA_UPDATE=force
rather 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.dtolnay/proc-macro2 (proc-macro2)
v1.0.89
Compare Source
serde-rs/serde (serde)
v1.0.213
Compare Source
with
attributes inside a newtype struct (#2847)v1.0.212
Compare Source
v1.0.211
Compare Source
with
anddefault
attributes (#2558, thanks @Mingun)dtolnay/syn (syn)
v2.0.85
Compare Source
v2.0.84
Compare Source
impl Sized + use<Self>
(#1772)v2.0.83
Compare Source
dtolnay/thiserror (thiserror)
v1.0.65
Compare Source
Configuration
📅 Schedule: Branch creation - "before 9am on monday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.