chore(deps): update all non-major dependencies - #2348
Conversation
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
The Linux artifact published with a -fips tag would move from AWS-LC-FIPS 3.x’s validated module to 4.x, which the dependency release notes say is still awaiting NIST certification. Pin aws-lc-rs below 1.18 before shipping to customers that require validated cryptography.
🤖 Datadog Autotest · Commit 78e1a9e · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
| [[package]] | ||
| name = "aws-lc-fips-sys" | ||
| version = "0.13.14" | ||
| version = "0.14.1" |
There was a problem hiding this comment.
Keep the validated module in FIPS images
Customers using the advertised -fips image could deploy a cryptographic module without a current NIST certificate, violating their compliance requirements.
Assertion details
- Input: Any Linux agent-data-plane image built with the
fipsfeature; release CI publishes both amd64 and arm64 variants with a-fipstag. - Expected: Constrain the workspace
aws-lc-rsdependency to<1.18, then regenerate Cargo.lock so Linux FIPS artifacts retain the validated 3.x module until 4.x is certified and approved. This is a multi-file generated-lockfile fix, so no inline suggestion is safe. - Actual: Cargo.lock upgrades
aws-lc-fips-sysfrom 0.13.14 to 0.14.1 throughaws-lc-rs1.18.0. The supplied upstream release notes state this switches from validated AWS-LC-FIPS 3.x to 4.x, which is awaiting NIST certification, and direct validation-required consumers to pin below 1.18. Existing tests only check approved algorithms and cannot detect certification status.
Was this helpful? React 👍 or 👎
🤖 Datadog Autotest · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
Regression Detector (Agent Data Plane)Optimization Goals:
|
This PR contains the following updates:
1.0.103→1.0.1041.0.1→1.1.01.9.1→1.9.20.4.42→0.4.430.1.89→0.1.921.17.1→1.18.01.12.0→1.12.12.4.0→2.7.04.6.1→4.6.60.3.12→0.3.130.3.32→0.3.330.3.341.4.2→1.5.01.0.1→1.1.00.1.3→0.1.40.1.51.10.1→1.11.04.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.10.23.41→0.23.431.14.1→1.15.11.0.228→1.0.2291.0.150→1.0.1513.21.0→3.22.00.9.1→0.9.20.6.4→0.6.51.52.3→1.53.10.7.18→0.7.190.1.15→0.1.161.0.117→1.0.1202.1.2→2.1.31.23.3→1.24.01.24.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
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.2Nullus157/async-compression (async-compression)
v0.4.43Compare Source
Other
dtolnay/async-trait (async-trait)
v0.1.92Compare Source
v0.1.91Compare Source
v0.1.90Compare Source
aws/aws-lc-rs (aws-lc-rs)
v1.18.0: aws-lc-rs v1.18.0Compare Source
AWS-LC-FIPS module updated to 4.x
This release switches
aws-lc-fips-sys(used via thefipsfeature) from the AWS-LC-FIPS 3.x branch to AWS-LC-FIPS 4.0.aws-lc-rsto<1.18.0. See the Cargo Book on Specifying Dependencies.What's Changed
aws-lc-fips-systo AWS-LC's "FIPS 4.0" branch by @justsmth in #1185aws-lc-fips-sysv0.13.16 -> v0.14.0. Please see the call-out above.PqdsaKeyPair,PqdsaPublicKey,PqdsaPrivateKey,PqdsaSigningAlgorithm,PqdsaVerificationAlgorithm, and theML_DSA_44/ML_DSA_65/ML_DSA_87algorithms (and their_SIGNINGcounterparts) now live inaws_lc_rs::signature. ML-DSA no longer requires theunstablefeature, and is now available underfips-- the FIPS 4.0 module provides ML-DSA, which is what had kept these APIs unstable. See our updated API documentation.aws_lc_rs::unstable::signaturetoaws_lc_rs::signature. Theunstable::signaturemodule remains as deprecated aliases and will be removed in a future release.PqdsaKeyPair::to_pkcs8has been renamed toto_pkcs8v1, since elsewhere in the module an unqualifiedto_pkcs8means PKCS#8 v2. A deprecatedto_pkcs8alias remains available under theunstablefeature.unstableconsumers continue to compile, with deprecation warnings. Two cases need a source change: builds using#![deny(warnings)], and code that glob-imports bothsignature::*andunstable::signature::*, which now needs an explicit import to disambiguate.PqdsaVerificationAlgorithm::parsed_verify_digest_signow always returnsUnspecified. Digest-then-verify is not an operation defined by FIPS 204 -- pure ML-DSA signs the message itself, and the pre-hash variant (HashML-DSA) uses a distinct domain separator that this API does not implement.seal_separate_out_of_placetoLessSafeKeyandTlsRecordSealingKey. Every sealing entry point was previously in-place, so a caller whose plaintext was borrowed or shared had to copy it into a scratch buffer purely to make it mutable. This mirrors the existingopen_separate_gather, so the sealing and opening directions now match.rsa::KeyPair::from_componentsfor constructing RSA key pairs from raw components by @justsmth in #1175rsa::KeyPairComponentsandrsa::KeyPair::from_components, matching ring 0.17, so a signing key can be built from formats such as JWK without first encoding the components as DER. Unlike ring,dand the CRT parameters are validated at construction usingRSA_check_key, so keys with inconsistent or placeholder values that ring accepts may be rejected. Unnecessary generic bounds were also removed fromPublicKeyComponents.OPENSSL_SMALL, and no AVX-512 assembly on x86_64) whenever Cargo is already building for size. In CI, a small binary exercising SHA-256, AES-256-GCM, and ECDSA P-256 is 36-50% smaller atopt-level=zthan atopt-level=3: 50% on x86_64 Linux, 48% on aarch64 macOS, 39% on x86_64 Windows, 36% on aarch64 Linux. Your own savings depend on how much of AWS-LC your binary retains.AWS_LC_SYS_SMALL=1/=0to force it on or off independently of opt-level.aws-lc-fips-sysrequires an explicitAWS_LC_FIPS_SYS_SMALL=1, and warns when it is set.opt-level=3footprint is unchanged.DEP_AWS_LC_*/DEP_AWS_LC_FIPS_*(libdir,libcrypto_path,link_kind, andlibssl_pathwithssl), consistently across the CC, CMake, and system-library build paths. Existing linker directives are unchanged. On Windows, the*_pathvalues are the link-time artifact (import library), not the runtime DLL.KeyEncryptionKey::unwrapno longer underflows on ciphertexts shorter than 8 bytes. Since the ciphertext is untrusted input, builds withoverflow-checks = truewould panic instead of returning the documentedErr(Unspecified); default release builds were unaffected.KeyEncryptionKeynow zeroizes its key material on drop, consistent with the other key types in this crate.Upstream AWS-LC (v5.5.0)
aws-lc-sysv0.44.0 aligns with AWS-LC v5.5.0 (previously v5.2.0). See also the release notes for v5.3.0 and v5.4.0.Build Improvements
OUT_DIRnow remove any stale destination first and leave the fresh copy writable, so building against a read-only prebuilt install (e.g. the Nix store) no longer fails withPermission deniedon a build-script rerun. AnOUT_DIRalready poisoned by an earlier build now recovers without acargo clean.Issues Being Closed
Other Merged PRs
New Contributors
Full Changelog: aws/aws-lc-rs@v1.17.3...v1.18.0
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.7.0Compare Source
ByteSize::display()when default features were disabled.v2.6.0Compare Source
v2.5.0Compare Source
#[no_alloc]support.v2.4.2Compare Source
v2.4.1Compare Source
clap-rs/clap (clap)
v4.6.6Compare Source
Features
Command::get_overridden_usagev4.6.5Compare Source
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 (http)
v1.5.0Compare Source
Method::QUERYconstant for the new QUERY method defined in RFC 10008.uri::Builder::path_and_query()to allow empty strings to mean no path.uri::PathAndQueryparsing to enforce URI max length.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
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.serde-rs/serde (serde)
v1.0.229Compare Source
serde-rs/json (serde_json)
v1.0.151Compare Source
jonasbb/serde_with (serde_with)
v3.22.0: serde_with v3.22.0Compare Source
Added
jiffv0.2 behind the newjiff_0_2feature flag (#936)jiff::SignedDurationworks withDurationSecondsand its variants.jiff::Timestamp,jiff::Zoned, andjiff::civil::DateTimework withTimestampSecondsand its variants.Deserializing a
jiff::Zoneduses the system time zone, likechrono::DateTime<Local>.Fixed
The
rust::sets_duplicate_value_is_error,rust::maps_duplicate_key_is_error,rust::sets_last_value_wins, andrust::maps_first_key_winsadapters created their backing sets/maps withwith_capacity_and_hasherusing the raw deserializersize_hint, bypassing thesize_hint_cautiouscap added in #966 (theclippy.tomldisallowed_methodslint only coversVec::with_capacity, notwith_capacity_and_hasher, so these sites were not flagged).Attacker-controlled input claiming a huge length could panic with
Hash table capacity overflowbefore a single element was read. All such constructions now route throughsize_hint_cautious.shepmaster/snafu (snafu)
v0.9.2Compare Source
Fixed
whatevermacro no longer triggers thesemicolon_in_expressions_from_macroslint.rust-lang/socket2 (socket2)
v0.6.5(#660).
(#663).
Socket::(set_)tos_v4on illumos(#662).
tokio-rs/tokio (tokio)
v1.53.1: Tokio v1.53.1Compare Source
1.53.1 (July 20th, 2026)
Fixed
OnceLock::waitfrom the Windows handler (#8300)Fixed (unstable)
Documented
v1.53.0: Tokio v1.53.0Compare Source
1.53.0 (July 17th, 2026)
Added
From<OwnedFd>andFrom<OwnedHandle>forFile([#8266])SocketAddrmethods to Unix sockets ([#8144])Changed
#[inline]to IO trait impls for in-memory types ([#8242])mpsc::{Receiver,UnboundedReceiver}now drops waker on drop, even if there are still senders ([#8095])#[track_caller]totimeout_at()([#8077])Sleep([#8132])Fixed
Chain([#8251])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.