chore(deps): update all non-major dependencies - #2209
Conversation
|
![datadog-prod-us1-6[bot]](https://avatars.githubusercontent.com/u/365230?s=60&v=4){kind=small}
There was a problem hiding this comment.
More details
The diff only changes pinned GitHub Action revisions and the default Rust toolchain; no changed behavior could be reproduced as a user-facing regression. Workflow YAML parses successfully, and the Rust pin remains compatible with the workspace's declared Rust 1.94 minimum.
📊 Validated against 4 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 481b584 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 481b584f4d
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -1,4 +1,4 @@ | |||
| [toolchain] | |||
| channel = "1.94.0" | |||
| channel = "1.97.1" | |||
There was a problem hiding this comment.
With Cargo.toml still advertising Rust 1.94 as the workspace MSRV, changing the directory override to 1.97.1 makes unqualified commands such as the GitLab make test jobs compile with 1.97.1 instead. This removes routine coverage of the supported compiler and allows later changes to use APIs or syntax unavailable to consumers on 1.94; keep this override at 1.94 or add an explicit 1.94 CI job before raising the development toolchain.
Useful? React with 👍 / 👎.
|
Regression Detector (Agent Data Plane)Run ID: Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (5)Experiments configured
Bounds Checks: ❌ Failed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
d0a388c to
242f2f3
Compare
242f2f3 to
ae1c8f8
Compare
This PR contains the following updates:
v6.0.3→v6.1.0v6.1.0→v6.2.0v6.4.0→v6.5.01.0.103→1.0.1041.0.1→1.1.01.9.1→1.9.20.1.89→0.1.911.17.1→1.17.31.12.0→1.12.12.4.0→2.4.24.6.1→4.6.40.3.12→0.3.130.3.32→0.3.331.0.1→1.1.00.1.3→0.1.41.10.1→1.11.01.1.0→1.1.14.0.0→4.2.00.2.186→0.2.1892.8.2→2.8.30.32.0→0.32.11.0.106→1.0.1071.0.45→1.0.470.10.1→0.10.21.12.4→1.13.11.94.0→1.97.10.23.41→0.23.421.14.1→1.15.01.15.11.0.228→1.0.2291.0.150→1.0.1510.9.1→0.9.20.6.4→0.6.52.0.117→2.0.1191.52.3→1.53.10.7.18→0.7.190.1.15→0.1.161.0.117→1.0.1182.1.2→2.1.31.23.3→1.24.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/checkout (actions/checkout)
v6.1.0Compare Source
actions/labeler (actions/labeler)
v6.2.0Compare Source
What's Changed
Bug Fix
Dependency Updates
Full Changelog: actions/labeler@v6.1.0...v6.2.0
actions/setup-node (actions/setup-node)
v6.5.0Compare Source
What's Changed
Full Changelog: actions/setup-node@v6.4.0...v6.5.0
dtolnay/anyhow (anyhow)
v1.0.104Compare Source
syndev-dependency to version 3reivilibre/anymap3 (anymap3)
v1.1.0Compare Source
Removals and Deprecations
Features
AnyDebugtrait from theanymorecrate. Enable withanymorecrate feature. Contributed by @DJMcNab — thank you. (#5)Internal Changes
TypeId. Runtime behaviour was unaffected. (#7)vorner/arc-swap (arc-swap)
v1.9.2dtolnay/async-trait (async-trait)
v0.1.91Compare Source
v0.1.90Compare Source
aws/aws-lc-rs (aws-lc-rs)
v1.17.3: aws-lc-rs v1.17.3Compare Source
What's Changed
awslc_version()returns the linked AWS-LC library version (e.g.,"5.1.0"), resolved at runtime.fips_version()returns the AWS-LC FIPS release-branch version asSome(version), orNonewhen unavailable. Note thatfips_version()is independent oftry_fips_mode().PqdsaKeyPairin serialized forms by @Mark-Simulacrum in #1174PqdsaKeyPair::from_seedin a FIPS setting, and notes that key pairs constructed from the expanded form cannot be re-serialized to PKCS#8 (which contains just the seed).Build Improvements
TARGET_*env leakage into host builds by @justsmth in #1171TARGET_CC/TARGET_CXX/TARGET_CFLAGSare now only applied when cross-compiling, andHOST_*variables are honored for native builds. Previously, whenaws-lc-sysappeared as both a dependency and a build-dependency in a cross build, the cross toolchain's flags leaked into the host-side build.rpmbuilddefaults): the memcmp probe (GCC bug 95189 check) now retains cc's computed target default flags (e.g.,-fPIC) while still excluding user CFLAGS. The check also only runs for GCC versions that may contain the bug, and a probe that fails to build only warns -- the build only fails when the miscompilation is actually demonstrated.Issues Being Closed
TARGET_CFLAGSapplied to host builds -- #1169Other Merged PRs
New Contributors
Full Changelog: aws/aws-lc-rs@v1.17.1...v1.17.3
v1.17.2Compare Source
tokio-rs/bytes (bytes)
v1.12.1Compare Source
Fixed
Box::newpanics (#837)bytesize-rs/bytesize (bytesize)
v2.4.2Compare Source
v2.4.1Compare Source
clap-rs/clap (clap)
v4.6.4Compare Source
Internal
v4.6.3Compare Source
Fixes
"literal".function()as attribute valuesv4.6.2Compare Source
Fixes
aliaswhen there is only onecrossbeam-rs/crossbeam (crossbeam-queue)
v0.3.13: crossbeam-queue 0.3.13Compare Source
push_mutandpop_muttoArrayQueueandSegQueue. (#1191)rust-lang/futures-rs (futures)
v0.3.33Compare Source
ReadLine's soundness issue regarding to exception safety. (#3020)Sendimpl forIterPinRefandIter. (#3003)compat01as03implementation. (#3012)FuturesUnordered::IntoIter. (#3005)portable-atomic-allocfeature and use it inFuturesUnordered. (#3007)alloc::task::Wake. (#3010)spinto 0.12. (#3014)hyperium/http-body (http-body)
v1.1.0Compare Source
tl;dr
AddforSizeHint.CopyforSizeHint.hyperium/hyper (hyper)
v1.11.0Compare Source
Bug Fixes
Upgradedwrites without send capacity (#4102) (aecf5abf)Features
ReadBufCursor::initialized_unfilled()method (#4115) (ccc1e850)v1.10.1 (2026-05-29)
Bug Fixes
metalbear-co/hyper-http-proxy (hyper-http-proxy)
v1.1.1Compare Source
kube-rs/kube (kube)
v4.2.0Compare Source
===================
rust-lang/libc (libc)
v0.2.189Compare Source
Added
pthread_sigmask,sigwait,sigwaitinfo,sigtimedwait,faccessat, andpthread_kill(#5270)clone3syscall (#4980)CLOCK_PROCESS_CPUTIME_IDandCLOCK_THREAD_CPUTIME_ID(#5274)Deprecated
CLONE_INTO_CGROUPandCLONE_CLEAR_SIGHAND. These overflow their types and will be changed to a larger size in the future. (8c6e6710458d)Fixed
wchar_tdefinition under Arm (#5245)time-related symbols (#5300)v0.2.188Compare Source
Changed
SendandSyncforDIR(35b062263401)These were removed in 0.2.187 because
libcdoes not actually makeSendandSyncguarantees about
DIR(or other extern types), but this caused some crates to break.The traits are added back for now to allow time to migrate, but will be removed again
in the future; please make sure your crates are not relying on
libc::DIR: Sendorlibc::DIR: Sync.v0.2.187Compare Source
This release contains a number of improvements related to 64-bit
time_tconfiguration.Of note the existing
RUST_LIBC_UNSTABLE_*environment variables have been replacedwith configuration options. The new way to use these is:
Being able to set this via
RUSTFLAGSmakes it easier to only apply configuration tospecific targets (and notably, not the host if build scripts are used).
There are two other notable changes:
The 32-bit
windows-gnutargets now respectlibc_unstable_gnu_time_bitsuClibc now supports a similar configuration option:
RUSTFLAGS='--cfg=libc_unstable_uclibc_time64'As a reminder, these options are under active development and may change in the future
(hence the "unstable" in the name). It likely that we will harmonize everything under a
single configuration option before considering them stable.
Support
aarch64-unknown-linux-pauthtest(#5065)Added
POSIX_SPAWN_*constants (#5104)getpwent,setpwent, andendpwent(#5160)preadv2andpwritev2(#5157)seccomp_notif*structures (#5224)timer_[create, delete, getoverrun, gettime, settime](#5108)PROC_PIDT_SHORTBSDINFOandproc_bsdshortinfo(#5110)SIOC*constants fromsockio.h(#5263)_IOR,_IOW,_IOWR(#5264)bpf_programandbpf_insn(#5235)kqueueconstants (#5077)vm_statistics64with recently added fields (#5253)IN6_IFF_*andSIOCGIFAFLAG_IN6(#5239)O_*,POSIX_FADV_*,NI*, and a few other missing constants (#5116)fdatasync,dlvsym,reallocarray,qsort_r,pthread_*affinity_np,ftok,extattr_*, anddup3(#5116)in6_pktinfo(#5256)DLT_*constants (#5235)PROC_LOGSIGEXIT_*andPPROT_*(#4657)SO_RERROR(#5260)IN6_IFF_*,in6_ifreq, andSIOCGIFAFLAG_IN6(#5239)_IO*helpers fromsys/ioccom.h(#5239)PTHREAD_*_MUTEX_INITIALIZER_NPfor riscv64 (#5094)struct tcp_info(#5215)OPEN_TREE_NAMESPACE(#5145)SECCOMP_IOCTL_*constants (#5224)SO_DETACH_REUSEPORT_BPF(#5081)futex_waitv(#5125)fsopen,fsconfig,fsmount, andfspick(#5145)statxpresent since 6.16 (#4621)ifaddrmsgandrtattr(#5234)sockaddr_iucv(#5041)ENOTCAPABLE(#4925)renameat2(#5113)F_SETFD(#5258)POLLRD*andPOLLWR*constants (#5258)SO_KEEPALIVEand TCP keepalive constants (#5111)TCP_MAXSEG(#5258)eventfdandEFD_*constants (#5258)pipe2(#5258)strerror_r(#5258)netinetstructs and constants (#5258)*atanddirentfunctions (#5117)port_alertandPORT_ALERT*constants (#5203)Deprecated
CPUCTL_RSMSRandUTX_DB_LASTLOG(#5116)Fixed
tsfrom*const timespecto*mut timespecin _lwp_park` (#5169)PTRACE_*ET_SYSCALL_USER_DISPATCH_CONFIGconstants fromu8toc_uint(#4936)cpuset_ttypo inCPU_ZERO(#5098)ifaddrs, pthread barriers, process sizing fields, andmcontextalignment (#5116)CPUCTL_CPUID*,EV_HUP, andEV_SYSFLAGS(#5116)POLLOUT(#5090)EPIOC[GS]PARAMSwith nonstandard _IOC (#5188)unsafe(#3727)__getmntinfo13(#5251)PTHREAD_MUTEX_INITIALIZER(#5241)Changed
-> c_void(#5240)AIO_LISTIO_MAXto account for changes in macOS 27 (#5253)MS_NOUSER(#5215)SW_MAXandSW_CNT(#5215)swapped_counttovm_statistics64(#4926)libc_unstable_gnu_time_bitsfor 64-bittime_tconfig (#5062)Removed
Elf32_Lword,ip_mreq_source, andIP_constants (#5116)KERN_REALROOTDEVandVM_LAPTOP_MODE(#5177)Other
LIBC_BUILD_VERBOSEis set (#5272)*LASTconstants as potentially changing (#5120)*MAXconstants as potentially changing (#5122)ELASTconstants as potentially changing (#5118)RAND_MAXas potentially changing (#5119)*NUMconstants as potentially changing (#5123)*COUNTconstants as potentially changing (#5121)time_t(#5046)RUST_LIBC_UNSTABLE_LINUX_TIME_BITS64(#5197)RUST_LIBC_UNSTABLEenv withlibc_unstable*cfg (#4977)BurntSushi/memchr (memchr)
v2.8.3Compare Source
open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)
v0.32.1Compare Source
Released 2026-Jun-26
dtolnay/proc-macro2 (proc-macro2)
v1.0.107Compare Source
dtolnay/quote (quote)
v1.0.47Compare Source
v1.0.46Compare Source
get_spaninquote_spanned(#329, thanks @Noratrieb)rust-random/rand (rand)
v0.10.2Compare Source
Fixes
UniformCharfrom bad source (#1790)Changes
partial_shuffleand apply#[must_use](#1769)unsafein contexts where non-local memory corruption could invalidate contract (#1791)rust-lang/regex (regex)
v1.13.1Compare Source
===================
This is a release that fixes a bug where incorrect regex match offsets could be
reported. Note that this doesn't impact whether a match occurs or not, just
where it occurs. The match offsets are still valid for slicing, they just may
not refer to the correct leftmost-first match. See
#1364 for (many) more details.
Bug fixes:
Fixes previously unsound reverse suffix and inner optimizations.
v1.13.0Compare Source
===================
This release includes a new API, a
regex!macro, for lazy compilation ofa regex from a string literal. If you use regexes a lot, it's likely you've
already written one exactly like it. The new macro can be used like this:
Improvements:
Add a new
regex!macro for efficient and automatic reuse of a compiled regex.rust-lang/rust (rust)
v1.97.1Compare Source
==========================
This backports an LLVM submodule bump to include the LLVM-side fix and a
revert of the rustc change that is one known trigger for the bug. The rustc
side revert should not be strictly necessary but is done out of abundance of caution.
v1.97.0Compare Source
==========================
Language
Result<T, Uninhabited>andControlFlow<Uninhabited, T>to be equivalent toTfor must use lintdead_code_pub_in_binarylint for unused pub items in binary cratesdiv32,lam-bh,lamcas,ld-seq-saandscqtarget featurescfg(target_has_atomic_primitive_alignment)selfin imports in more casesPlatform Support
Refer to Rust's platform support page
for more information on Rust's tiered platform support.
Stabilized APIs
Default for RepeatNCopy for ffi::FromBytesUntilNulErrorSend for std::fs::Fileon UEFI<{integer}>::isolate_highest_one<{integer}>::isolate_lowest_one<{integer}>::highest_one<{integer}>::lowest_one<{integer}>::bit_widthNonZero<{integer}>::isolate_highest_oneNonZero<{integer}>::isolate_lowest_oneNonZero<{integer}>::highest_oneNonZero<{integer}>::lowest_oneNonZero<{integer}>::bit_widthThese previously stable APIs are now stable in const contexts:
char::is_controlCargo
build.warningsconfig. This controls how lint warnings from local packages are treated. Useful for enforcing a warning-free build in CI, replacing-Dwarnings. docsresolver.lockfile-pathconfig. This allows specifying the path to the lockfile to use when resolving dependencies. Useful when working with read-only source directories. docs--target-dirdoesn't look like a Cargo target directory. This prevents accidental deletion of non-target directories.-mshorthand for--manifest-pathcurldependency fromcrates-iocrateRustdoc
--emitflag--remap-path-prefixCompatibility Notes
f32: From<{float}>to constrain{float}pin!, in order to prevent unsoundness. The most likely case where this might impact users is: writingpin!(x)wherexhas type&mut Twill now always correctly produce a value of typePin<&mut &mut T>, instead of sometimes allowing a coercion that produces a value of typePin<&mut T>. This coercion was previously incorrectly allowed since Rust 1.88.0.std::charconstants and functionsf64methods which have been deprecated since 1.0varargs_without_patternlint in depslink_sectionspecifierenums have changed. This is not a breaking change, as it only applies toenums without layout guarantees, but is noted here as we've seen people impacted from having made assumptions about the layout algorithm.#[export_name = "..."]where the name is empty#[link_name = "..."]&#[link(name = "...")]parametersshutdownon a socket to shut down the write side, attempting to write to the socket will now produce aBrokenPipeerror rather thanOther. MapWSAESHUTDOWNtoio::ErrorKind::BrokenPipev1.96.1Compare Source
===========================
v1.96.0Compare Source
==========================
Language
exprmetavariable tocfgManuallyDropas patterns (fixing a regression introduced in 1.94.0)Compiler
riscv64gc-unknown-fuchsiabaseline to RVA22 + vectorLibraries
NonZerointegersStabilized APIs
assert_matches!debug_assert_matches!From<T> for AssertUnwindSafe<T>From<T> for LazyCell<T, F>From<T> for LazyLock<T, F>core::range::RangeToInclusivecore::range::RangeToInclusiveItercore::range::RangeFromcore::range::RangeFromItercore::range::Rangecore::range::RangeIterCargo
target.'cfg(..)'.rustdocflagssupport in configuration.Rustdoc
white-space: pre-wrap;property and stripped any<p>elements from the rendered html, however this caused issues and unintuitive behavior. The new behavior should be more predictable, however some multi-line deprecation notes will now be rendered as as single lines. If this is undesirable, you can use the standard markdown method of forcing a linebreak, which is two spaces followed by a newline ("\n").missing_doc_code_exampleslint on impl itemsCompatibility Notes
#[repr(Int)]enums in some edge cases involving fields of uninhabited zero-sized typesPin<Foo>whereFoodoesn't implementDeref. Some such coercions were previously allowed, but produce a type with no useful public API.--allow-undefinedon wasm targets#![reexport_test_harness_main]attributeuninhabited_staticlint in dependencies and make it deny-by-defaultThis appears to improve the quality of backtraces. This change has no effect on the defaults for the output of rustc/cargo on these targets.
-Csoft-float::{self [as name]}, e.g.,struct S {}; use S::{self as Other};, is now no longer permitted because{self}imports require a module parent.export_name,link_name, andlink_sectionattributes, if multiple of the same attribute is present, the first one now takes precedence.avrtargets, C'sdoubletype is 32-bit by default, so changec_doubletof32onavrtargets to match. This is a breaking change, but necessary to makec_doublematch C's double.Internal Changes
These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.
aarch64softfloat targets now have to haverustc_abiset to"softfloat"cfg(target_abi)v1.95.0[Compare Source](https://redirect.github.c
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 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.