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:
1.41.1
->1.42.0
0.13.0
->0.14.0
0.11.2
->0.11.3
0.2.25
->0.2.27
1.0.134
->1.0.135
2.0.93
->2.0.95
Release Notes
mitsuhiko/insta (insta)
v1.42.0
Compare Source
snapshot_type: text
in 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-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
cargo-insta
before running tests. Instead, running a test will overwrite orremove its own pending snapshot. To remove all pending snapshots, use
cargo insta reject
or 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
rust-itertools/itertools (itertools)
v0.14.0
Compare Source
Breaking
cons_tuples
(#988)Added
array_combinations
(#991)k_smallest_relaxed
and variants (#925)next_array
andcollect_array
(#560)DoubleEndedIterator
forFilterOk
(#948)DoubleEndedIterator
forFilterMapOk
(#950)Changed
Q: ?Sized
inItertools::contains
(#971)chain!
(#943)into_group_map_by
documentation (#1000)tree_reduce
documentation (#955)merge_join_by
(#966)take_while_inclusive
(#972)find_or_last
andfind_or_first
(#984)tuple_combinations
(#945)track_caller
attr forasser_equal
(#976)Notable Internal Changes
default_features
inCargo.toml
todefault-features
(#985)rust-phf/rust-phf (phf)
v0.11.3
Compare Source
dtolnay/prettyplease (prettyplease)
v0.2.27
Compare Source
v0.2.26
Compare Source
serde-rs/json (serde_json)
v1.0.135
Compare Source
dtolnay/syn (syn)
v2.0.95
Compare Source
v2.0.94
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.