Repository navigation
chore(deps): update rust - #614
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #614 +/- ##
=======================================
Coverage 98.09% 98.09%
=======================================
Files 34 34
Lines 7547 7547
=======================================
Hits 7403 7403
Misses 144 144
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/rust
branch
from
October 17, 2026 22:29
8cfde0e to
eb8e246
Compare
This branch has not been deployed
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:
1.25.2→1.25.31.26.00.9.146→0.9.1481.0.151→1.0.1521.0.154(+1)Release Notes
cargo-bins/cargo-binstall (aqua:cargo-bins/cargo-binstall)
v1.25.3Compare Source
Binstall is a tool to fetch and install Rust-based executables as binaries. It aims to be a drop-in replacement for
cargo installin most cases. Install it today withcargo install cargo-binstall, from the binaries below, or if you already have it, upgrade withcargo binstall cargo-binstall.In this release:
Other changes:
nextest-rs/nextest (cargo:cargo-nextest)
v0.9.148: cargo-nextest 0.9.148Compare Source
Changed
slow-timeoutno longer acceptson-timeout = "pass", and nextest now reports a configuration error if it is specified. A setup script that times out always fails the run. Previously, this setting was accepted but handled inconsistently: the timed-out script was counted as a failure, but the run was not cancelled. (#3640)guppyupdated to 0.19.1, andtarget-specupdated to 3.7.0, updating built-in targets to Rust 1.98.Fixed
Stress runs now exit with a non-zero code if any iteration failed. Previously, with fail-fast disabled, the exit code reflected only the last iteration, so a stress run with failures in earlier iterations exited with code 0 if the last iteration passed. (#3624)
Stress runs now always run at least one iteration. Previously,
--stress-durationwith a very short duration (such as1ns) could finish without running any tests. (#3633)Runs stopped by immediate fail-fast (
--max-fail N:immediate) are now treated as failed rather than cancelled. Previously, in stress runs, the summary read0 passed; cancelled due to test failureand the failing iteration was not counted as failed. (#3639)When the global timeout fires with immediate fail-fast enabled, nextest now reports the global timeout as the reason the run was cancelled. Previously, the tests terminated by the timeout counted as failures, so nextest printed a second
Cancelling due to test failureline and reported a test failure as the reason. (#3637)After the global timeout fires, nextest no longer keeps a CPU core busy while it waits for running tests to shut down. (#3647)
The leak timeout is no longer restarted each time a leaked handle produces output, or each time nextest handles a signal or an info request while waiting. Previously, a test that exited while leaving behind a process that kept writing to standard output or standard error could delay leak detection indefinitely. (#3646)
If waiting on a test or setup script process fails, nextest now reports the test or script as an execution failure, with the underlying error shown. Previously, nextest panicked. (#3643)
The
CancellingandKillingstatus lines no longer contain stray colons. Previously, nextest printed lines likeKilling due to second signal: : 1 test still running, and a trailing colon when nothing was still running. (#3641)Internal improvements
Source builds of nextest no longer compile two versions of
zstd. (#3620)Thanks Jake-Shadle for your contribution!
serde-rs/json (serde_json)
v1.0.152Compare Source
-0in arbitrary_precision mode (#1346, thanks @yuxi-liu-wired)Configuration
📅 Schedule: (UTC)
🚦 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.