-
-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update cargo #272
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
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/cargo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
aaec139 to
6994d22
Compare
6994d22 to
631f287
Compare
10adf58 to
a766d9e
Compare
a766d9e to
2954bd0
Compare
b524a83 to
c2600e3
Compare
8fb8f49 to
b2824bd
Compare
6e4e08c to
fa7dd2c
Compare
0a32f49 to
06927f0
Compare
|
Coverage after merging renovate/cargo into main will be
Coverage Report
|
|||||||||||||||||||||||||||||||||||||||||||||||||
06927f0 to
4376058
Compare
Contributor
Author
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.10.0→1.12.14.5.18→4.5.550.19.0→0.20.02.0.5→2.0.71.40.0→1.46.11.0.210→1.0.2283.12.0→3.24.0Release Notes
BurntSushi/bstr (bstr)
v1.12.1Compare Source
v1.12.0Compare Source
v1.11.3Compare Source
v1.11.2Compare Source
v1.11.1Compare Source
v1.11.0Compare Source
clap-rs/clap (clap)
v4.5.55Compare Source
v4.5.54Compare Source
Fixes
[default]to its own paragraph whenPossibleValue::helpis present in--helpv4.5.53Compare Source
Features
default_values_if,default_values_ifsv4.5.52Compare Source
Fixes
args_conflicts_with_subcommandsconflicts with anArgGroupv4.5.51Compare Source
Fixes
ArgAction::Countv4.5.50Compare Source
Features
CowwhereStringand&strare acceptedv4.5.49Compare Source
Fixes
v4.5.48Compare Source
Documentation
typed_derivecookbook entryv4.5.47Compare Source
Features
impl FromArgMatches for ()impl Args for ()impl Subcommand for ()impl FromArgMatches for Infallibleimpl Subcommand for InfallibleFixes
clapv4.5.46Compare Source
Features
StyledStr::push_strv4.5.45Compare Source
Fixes
ValueEnumvariants now use the full doc comment, not summary, forPossibleValue::helpv4.5.44Compare Source
Features
Command::mut_subcommandsv4.5.43Compare Source
Fixes
v4.5.42Compare Source
Fixes
--helpv4.5.41Compare Source
Features
Styles::contextandStyles::context_valueto customize the styling of[default: value]like notes in the--helpv4.5.40Compare Source
Features
arg!()macro (e.g.arg!("check-config": ...))v4.5.39Compare Source
Fixes
v4.5.38Compare Source
Fixes
--or-v4.5.37Compare Source
Features
ArgMatches::try_clear_id()v4.5.36Compare Source
Fixes
v4.5.35Compare Source
Fixes
help_headingv4.5.34Compare Source
Fixes
flatten_help(true)and subcommands without argumentsv4.5.33Compare Source
Fixes
v4.5.32Compare Source
Features
Error::removeDocumentation
humantimetojiffInternal
pulldown-cmarkv4.5.31Compare Source
Features
ValueParserFactoryforSaturating<T>v4.5.30Compare Source
Fixes
num_args(0..=1)to be used withSetTruetakes_valuesassertionsv4.5.29Compare Source
Fixes
ArgMatches::args_presentso not-present flags are considered not-present (matching the documentation)v4.5.28Compare Source
Features
unstable-markdownv4.5.27Compare Source
Documentation
v4.5.26Compare Source
Fixes
suggestionsfeaturev4.5.25Compare Source
Fixes
v4.5.24Compare Source
Fixes
ignore_errors(true)and when a suggestion is provided for an unknown argumentv4.5.23Compare Source
Fixes
allow_negative_numbers, allowEagainv4.5.22Compare Source
Fixes
v4.5.21Compare Source
Fixes
ignore_errors(true)v4.5.20Compare Source
Features
CommandExtv4.5.19Compare Source
Internal
rust-lang/git2-rs (git2)
v0.20.3Compare Source
v0.20.2Compare Source
0.20.1...0.20.2
Added
Status::WT_UNREADABLE.#1151
Fixed
GIT_EDIRECTORY,GIT_EMERGECONFLICT,GIT_EUNCHANGED,GIT_ENOTSUPPORTED, andGIT_EREADONLYtoError::raw_code.#1153
Indexer::new.#1160
v0.20.1Compare Source
0.20.1...0.20.2
Added
Status::WT_UNREADABLE.#1151
Fixed
GIT_EDIRECTORY,GIT_EMERGECONFLICT,GIT_EUNCHANGED,GIT_ENOTSUPPORTED, andGIT_EREADONLYtoError::raw_code.#1153
Indexer::new.#1160
v0.20.0Compare Source
0.20.0...0.20.1
Added
Repository::branch_upstream_merge()#1131
Index::conflict_get()#1134
Index::conflict_remove()#1133
opts::set_cache_object_limit()#1118
Repo::merge_file_from_index()and associatedMergeFileOptionsandMergeFileResult.#1062
Changed
urldependency minimum raised to 2.5.4#1128
#1121
CredentialHelper::config) now checks for helpers that start with something that looks like an absolute path, rather than checking for a/or\anywhere in the helper string (which resolves an issue if the helper had arguments with/or\).#1137
Fixed
Remote::url_bytesif the url is empty.#1120
Patch::delta,Patch::hunk, andPatch::line_in_hunk. The return values must not outlive thePatch.#1141
#1143
dtolnay/indoc (indoc)
v2.0.7Compare Source
indoc! {c"..."},indoc! {cr"..."}(#67)v2.0.6Compare Source
mitsuhiko/insta (insta)
v1.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.serde-rs/serde (serde)
v1.0.228Compare Source
RUSTDOCFLAGS='--cfg=docsrs'set for the whole dependency graph (#2995)v1.0.227Compare Source
v1.0.226Compare Source
v1.0.225Compare Source
v1.0.224Compare Source
v1.0.223Compare Source
v1.0.222Compare Source
serialize_withattribute produce code that works if respanned to 2024 edition (#2950, thanks @aytey)v1.0.221Compare Source
serde_if_integer128!macro (#2975)v1.0.220Compare Source
v1.0.219Compare Source
absolute_pathsClippy restriction being triggered inside macro-generated code (#2906, thanks @davidzeng0)v1.0.218Compare Source
v1.0.217Compare Source
v1.0.216Compare Source
v1.0.215Compare Source
v1.0.214Compare Source
v1.0.213Compare Source
withattributes inside a newtype struct (#2847)v1.0.212Compare Source
v1.0.211Compare Source
withanddefaultattributes (#2558, thanks @Mingun)Stebalien/tempfile (tempfile)
v3.24.0Compare Source
v3.23.0Compare Source
v3.22.0Compare Source
windows-sysrequirement to allow version 0.61.xunstable-windows-keep-open-tempfilefeature.v3.21.0Compare Source
windows-sysrequirement to allow version 0.60.xv3.20.0Compare Source
This release mostly unifies the behavior/capabilities around "keeping" temporary files:
Builder::keep(bool)(via deprecation) toBuilder::disable_cleanup(bool)to make it clear that behaves differently fromNamedTempFile::keep(). The former disables automatic cleanup while the latter consumes theNamedTempFileobject entirely and unsets the "temporary file" attribute (on Windows).TempDir::into_path(via deprecation) toTempDir::keepto mirrorNamedTempFile::keep.TempDir::disable_cleanup,NamedTempFile::disable_cleanup, andTempPath::disable_cleanupmaking it possible to disable automatic cleanup in-place after creating a temporary file/directory (equivalent to callingBuilder::disable_cleanupbefore creating the file/directory).Additionally, it adds a few spooled temporary file features:
git lo
SpooledTempFile::into_filefor turning aSpooledTempFileinto a regular unnamed temporary file, writing it to the backing storage ("rolling" it) if it was still stored in-memory.spooled_tempfile_inandSpooledTempFile::new_inmethods for creating spooled temporary files in a specific directory. This makes it possible to choose the backing device for your spooled temporary file which is rather important on Linux where the default temporary directory is likely backed by memory (defeating the entire point of having a spooled temporary file).Finally, this release improves documentation, especially the top-level documentation explaining which temporary file type to use.
BREAKING for those with
deny(warnings):Builder::keepdeprecated in favor ofBuilder::disable_cleanup.TempDir::into_pathis deprecated in favor ofTempDir::keep.v3.19.1Compare Source
v3.19.0Compare Source
cfg-if. It's still in the tree, but we didn't really need to use it in this crate.unstable-windows-keep-open-tempfile) to test a potential fix to #339.v3.18.0Compare Source
rustixto 1.0.0.NamedTempFile::persist_noclobberatomic on Apple operating systems. It's now atomic on MacOS, Windows, and Linux (depending on the OS version and filesystem used).v3.17.1Compare Source
windows-sys0.52. Unfortunately, we have no CI for olderwindows-sysversions at the moment...v3.17.0Compare Source
Builder::make_in(when creating temporary files of arbitrary types).getrandom, use platform (e.g., CPU) specific randomness sources where possible.v3.16.0Compare Source
getrandomto0.3.0(thanks to @paolobarbolini).windows-sysversions0.59.xin addition to0.59.0(thanks @ErichDonGubler).v3.15.0Compare Source
Re-seed the per-thread RNG from system randomness when we repeatedly fail to create temporary files (#314). This resolves a potential DoS vector (#178) while avoiding
getrandomin the common case where it's necessary. The feature is optional but enabled by default via thegetrandomfeature.For libc-free builds, you'll either need to disable this feature or opt-in to a different
getrandombackend.v3.14.0Compare Source
v3.13.0Compare Source
with_suffixconstructors for easily creating new temporary files with a specific suffix (e.g., a specific file extension). Thanks to @Borgerr.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.
👻 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.