build(deps): bump the cargo group across 1 directory with 87 updates

[dependabot]

Bumps the cargo group with 87 updates in the / directory:

Package	From	To
expectrl	0.8.0	0.9.0
cached	0.59.0	2.0.2
itertools	0.14.0	0.15.0
uucore	0.8.0	0.9.0
uu_arch	0.8.0	0.9.0
uu_base32	0.8.0	0.9.0
uu_base64	0.8.0	0.9.0
uu_basename	0.8.0	0.9.0
uu_basenc	0.8.0	0.9.0
uu_cat	0.8.0	0.9.0
uu_cksum	0.8.0	0.9.0
uu_b2sum	0.8.0	0.9.0
uu_md5sum	0.8.0	0.9.0
uu_sha1sum	0.8.0	0.9.0
uu_sha224sum	0.8.0	0.9.0
uu_sha256sum	0.8.0	0.9.0
uu_sha384sum	0.8.0	0.9.0
uu_sha512sum	0.8.0	0.9.0
uu_comm	0.8.0	0.9.0
uu_cp	0.8.0	0.9.0
uu_csplit	0.8.0	0.9.0
uu_cut	0.8.0	0.9.0
uu_date	0.8.0	0.9.0
uu_dd	0.8.0	0.9.0
uu_df	0.8.0	0.9.0
uu_dir	0.8.0	0.9.0
uu_dircolors	0.8.0	0.9.0
uu_dirname	0.8.0	0.9.0
uu_du	0.8.0	0.9.0
uu_echo	0.8.0	0.9.0
uu_env	0.8.0	0.9.0
uu_expand	0.8.0	0.9.0
uu_expr	0.8.0	0.9.0
uu_factor	0.8.0	0.9.0
uu_false	0.8.0	0.9.0
uu_fmt	0.8.0	0.9.0
uu_fold	0.8.0	0.9.0
uu_head	0.8.0	0.9.0
uu_hostname	0.8.0	0.9.0
uu_join	0.8.0	0.9.0
uu_link	0.8.0	0.9.0
uu_ln	0.8.0	0.9.0
uu_ls	0.8.0	0.9.0
uu_mkdir	0.8.0	0.9.0
uu_mktemp	0.8.0	0.9.0
uu_more	0.8.0	0.9.0
uu_mv	0.8.0	0.9.0
uu_nl	0.8.0	0.9.0
uu_nproc	0.8.0	0.9.0
uu_numfmt	0.8.0	0.9.0
uu_od	0.8.0	0.9.0
uu_paste	0.8.0	0.9.0
uu_pr	0.8.0	0.9.0
uu_printenv	0.8.0	0.9.0
uu_printf	0.8.0	0.9.0
uu_ptx	0.8.0	0.9.0
uu_pwd	0.8.0	0.9.0
uu_readlink	0.8.0	0.9.0
uu_realpath	0.8.0	0.9.0
uu_rm	0.8.0	0.9.0
uu_rmdir	0.8.0	0.9.0
uu_seq	0.8.0	0.9.0
uu_shred	0.8.0	0.9.0
uu_shuf	0.8.0	0.9.0
uu_sleep	0.8.0	0.9.0
uu_sort	0.8.0	0.9.0
uu_split	0.8.0	0.9.0
uu_sum	0.8.0	0.9.0
uu_sync	0.8.0	0.9.0
uu_tac	0.8.0	0.9.0
uu_tail	0.8.0	0.9.0
uu_tee	0.8.0	0.9.0
uu_test	0.8.0	0.9.0
uu_touch	0.8.0	0.9.0
uu_tr	0.8.0	0.9.0
uu_true	0.8.0	0.9.0
uu_truncate	0.8.0	0.9.0
uu_tsort	0.8.0	0.9.0
uu_uname	0.8.0	0.9.0
uu_unexpand	0.8.0	0.9.0
uu_uniq	0.8.0	0.9.0
uu_unlink	0.8.0	0.9.0
uu_vdir	0.8.0	0.9.0
uu_wc	0.8.0	0.9.0
uu_whoami	0.8.0	0.9.0
uu_yes	0.8.0	0.9.0
reedline	0.47.0	0.49.0

Updates expectrl from 0.8.0 to 0.9.0

Commits

• See full diff in compare view

Updates cached from 0.59.0 to 2.0.2

Changelog

Sourced from cached's changelog.

[2.0.2]

• Docs/tests only (no API change): document the Expires trait / expires = true as the idiomatic way to set a dynamic, per-entry TTL (a lifetime computed at call time rather than the uniform ttl = N), with a runnable example reference, and add a regression test for the runtime-argument-driven TTL case (#246).

[2.0.1]

• Fix TtlSortedCacheBuilder: an explicit .capacity(n) is now honored even when .max_size(m) is also set. Previously the max_size-derived m + 1 preallocation ran first, and because HashMap::reserve never shrinks, a smaller .capacity(n) had no effect. The explicit capacity now takes precedence as the preallocation hint while max_size continues to bound entry count (#266).

[2.0.0 / cached_proc_macro 2.0.0]

Upgrading from 1.1? See the 2.0 migration guide.

Breaking Changes

Minimum supported Rust version & edition

• MSRV raised from 1.80 to 1.85, and the crates moved to the 2024 edition. Edition 2024 was stabilized in Rust 1.85, so this is the new minimum a downstream project needs to build cached. Consumers already on Rust ≥ 1.85 are unaffected; those on 1.80–1.84 must update their toolchain. (The repository's rust-toolchain.toml pins the latest stable for local development and CI only — that pin does not propagate to consumers.)

Trait API changes

• Cached::cache_remove_entry<Q>(&mut self, k: &Q) -> Option<(K, V)>: new required method on the Cached trait that removes an entry and returns the stored key and value. Unlike cache_remove, this returns Some even when the deleted entry was already expired, making it possible to distinguish "key absent" from "key present but expired". Always fires the store's on_evict callback (if set).
• ConcurrentCached::cache_remove_entry(&self, k: &K) -> Result<Option<(K, V)>, Self::Error>: same semantics on the concurrent trait; implemented for all nine concurrent stores (six sharded plus DiskCache / RedisCache / AsyncRedisCache). The seven non-sharded stores (UnboundCache, LruCache, etc.) gain cache_remove_entry via the Cached trait above.
• Cached::cache_delete<Q>(&mut self, k: &Q) -> bool: new default method on Cached that deletes an entry without returning it; returns true if an entry was physically removed (including expired entries), false if the key was absent. Implemented via cache_remove_entry.
• DiskCache and RedisCache / AsyncRedisCache now require K: Clone (in addition to existing bounds) for their ConcurrentCached / ConcurrentCachedAsync impls, which is needed to return the stored key from cache_remove_entry.
• ConcurrentCached / ConcurrentCachedAsync mutators now take &self instead of &mut self: set_refresh_on_hit, set_ttl, and unset_ttl are defined with a shared receiver, matching the internally-synchronized &self contract of the rest of these traits (cache_set, cache_remove, …). This lets you flip the refresh flag or change the TTL on a shared store (e.g. one behind an Arc or a static) without exclusive access. Implementors must update their method signatures (fn set_ttl(&self, …) etc.); the bundled DiskCache / RedisCache / AsyncRedisCache stores do this via interior mutability (parking_lot::Mutex + AtomicBool). The single-owner Cached and CacheTtl traits are unaffected and keep their &mut self mutators.
• ConcurrentCached::cache_size / ConcurrentCachedAsync::cache_size: new method fn cache_size(&self) -> Result<Option<usize>, Self::Error> reporting the number of entries, with a default of Ok(None). The default makes it non-breaking for existing external implementors and honest for stores that cannot cheaply produce a count: the six sharded stores override it to return Ok(Some(len)), while the external-store impls (DiskCache, RedisCache, AsyncRedisCache) keep the Ok(None) default because their backends (redb, Redis) expose no O(1) size. Sharded stores also retain their inherent len() / is_empty() for a non-Result count.

Macro attribute changes (#[cached], #[once], #[concurrent_cached])

• result = true removed from #[cached] and #[once]: All Result<T, E> return types now automatically skip caching Err values. Remove result = true from all #[cached] and #[once] annotations — the behavior is now the default. To force-cache Err values, use the new cache_err = true opt-in.
• option = true removed from #[cached] and #[once]: All Option<T> return types now automatically skip caching None values. Remove option = true from all #[cached] and #[once] annotations — the behavior is now the default. To force-cache None values, use the new cache_none = true opt-in.
• #[concurrent_cached] now supports Option<T> returns: previously only Result<T, E> was accepted; Option<T> and plain T: Clone returns are now natively supported on the default in-memory sharded path. Note: option = true was never a recognized attribute on #[concurrent_cached] (it was silently ignored in 1.x); the new cache_none = true is the explicit opt-in to cache None values.
• #[cached] / #[once] on fn() -> Option<T> without attributes: previously cached None as-is; now skips caching None. Add cache_none = true to preserve the old behavior.
• #[cached] / #[once] on fn() -> Result<T,E> without attributes: previously cached the full Result; now skips caching Err. Add cache_err = true to preserve the old behavior.
• result_fallback = true no longer requires result = true: the explicit result = true companion is dropped; result_fallback now auto-detects Result<T,E> return types.
• Custom-ty users storing Option<T> or Result<T,E> directly: if your cache store type holds Option<T> or Result<T,E> as the value, you must now add cache_none = true or cache_err = true respectively so the macro uses the full wrapper type rather than extracting the inner T.
• map_error on the default in-memory sharded path is now a compile error: previously map_error = "…" was silently accepted and ignored when the store was the infallible default. If you had map_error on a #[concurrent_cached] that uses no redis/disk/ty/create, remove it. If you still need map_error (because you are switching to a redis or disk backend), add the corresponding backend attribute.
• result_fallback = true and with_cached_flag = true are mutually exclusive on #[concurrent_cached]: using both together is now a compile error. The combination was never valid — result_fallback stores the inner Ok(T) value while with_cached_flag wraps it in Return<T> — but the error was previously inscrutable. Remove one of the two attributes.
• cache_none = true and with_cached_flag = true are mutually exclusive on #[cached], #[once], and #[concurrent_cached]: using both together is now a compile error. The combination was never valid — cache_none = true stores Option<T> as the cached value type while with_cached_flag = true stores the inner T — but the error was previously a confusing downstream type mismatch. Remove one of the two attributes.

Store behavior changes

• cache_remove on expiring stores now returns None for expired-but-present entries. Previously ExpiringCache, ExpiringLruCache, and expiry-aware sharded stores returned Some(value) for an already-expired entry; now returns None. The entry is still removed and on_evict still fires.
• ConcurrentCached::cache_delete (and its ConcurrentCachedAsync equivalent) now returns true for expired-but-physically-present entries. In 1.x the method returned false for such entries. Use cache_remove if you need to distinguish a live removal from an expired one.
• LruCache::retain now fires on_evict and increments cache_evictions() for each removed entry, matching the semantics of cache_remove. Previously retain was side-effect-free. Internal TTL and expiring wrapper stores (LruTtlCache, ExpiringLruCache) use a new crate-internal retain_silent for their eviction sweeps, so those stores continue to count evictions exactly once.
• DiskCacheBuildError gains a new InvalidTtl(BuildError) variant: any exhaustive match on DiskCacheBuildError must add an arm for InvalidTtl. This variant is returned when a DiskCacheBuilder is given a zero-duration TTL.
• RedisCacheBuildError gains a new InvalidTtl(BuildError) variant: same as above for RedisCacheBuildError. Returned when a RedisCacheBuilder is given a zero-duration TTL.

Builder-only construction — build() returns Result, all store constructors removed

• Every store is now built exactly one way: X::builder().…setters….build()?. All direct, store-returning constructors are removed — new, with_capacity, with_max_size, with_ttl, with_ttl_and_capacity, with_ttl_and_refresh, with_max_size_and_ttl, with_max_size_and_ttl_and_refresh, every try_with_*, and the sharded new / with_shards / with_max_size[_and_shards] / with_ttl[_and_shards] / with_max_size_and_ttl[_and_shards] variants — across UnboundCache, LruCache, TtlCache, LruTtlCache, TtlSortedCache, ExpiringCache, ExpiringLruCache, and all six sharded stores. (DiskCache / RedisCache / AsyncRedisCache are unchanged: their new(...) / builder(...) already return a builder.) This removes the second, panic-prone construction path that duplicated the builder.
• Builder::build now returns Result<Store, BuildError> for every in-memory and sharded store. It previously returned the store directly and panicked on invalid configuration. Add ? or .unwrap(). (Disk/Redis build() already returned Result; unchanged.)
• try_build() is removed from all builders. Now that build() is the single fallible constructor the alias is redundant — replace every .try_build() with .build().
• TtlSortedCacheBuilder gains .capacity(n) — the preallocation hint formerly supplied via TtlSortedCache::with_ttl_and_capacity. It is distinct from .max_size(n), which is the eviction bound.
• Zero TTL is now always rejected. Because every store is built through its (validating) builder, a zero Duration yields BuildError::InvalidTtl. The previously-permissive direct constructors (e.g. TtlCache::with_ttl(Duration::ZERO)) that accepted a zero TTL no longer exist.

size → max_size naming (builder setter, macro attribute, runtime setters)

• Builder setter .size(n) → .max_size(n) (LRU-family stores and TtlSortedCache). The sharded builders' per-shard cap setter is per_shard_max_size.

... (truncated)

Commits

• See full diff in compare view

Updates itertools from 0.14.0 to 0.15.0

Changelog

Sourced from itertools's changelog.

0.15.0

Breaking

• Restructure Position as struct instead of enum (#1042, #1043)
• Canonicalize all_equal_value's error type (#1032)

Added

• Add *_with_hasher adaptors (#1007)
• Add strip_prefix and strip_prefix_by methods (#1104)

Changed

• Remove Clone bounds from tuple_combinations and array_combinations(#1011)
• must_use for collect_vec (#1009)
• Make izip! temporary friendly (#1021)
• Add array_combinations_with_replacement (#1033)
• Implement Debug for remaining public types (#1038)
• Specialize ExactlyOneError::count (#1046)
• Implement PeekingNext for more types, in particular vec::IntoIter (#1059, #1073)
• Fix PadUsing::next_back (#1082)
• Introduce [circular_]array_windows, deprecate tuple_windows (#1086)
• Deprecate tuple_combinations (replaced by array_combinations) (#1085)

Notable Internal Changes

• Make into_group_map code more idiomatic (#1027)
• Fix clippy lints (#1017, #1029, #1076, #1099)

Commits

• 37bd72a Update CHANGELOG.md: strip_prefix[_by]
• 86ec635 Use ControlFlow in fold_while implementation
• d5897f7 refactor(strip_prefix): use try_for_each and drop PartialEq, Eq on StripPrefi...
• b2a978a feat(Itertools): add strip_prefix and strip_prefix_by methods
• 12b6ec6 Update CHANGELOG.md for all_equal_value_error's error type
• 121821e AllEqualValueError implements std::error::Error
• adac44e Introduce AllEqualValueError
• 5707384 Update CHANGELOG.md
• df60ff0 Update CHANGELOG.md
• 113b850 Update CHANGELOG.md to include with_hasher
• Additional commits viewable in compare view

Updates uucore from 0.8.0 to 0.9.0

Release notes

Sourced from uucore's releases.

0.9.0

Rust Coreutils 0.9.0 Release:

We are excited to announce the release of Rust Coreutils 0.9.0 - a release focused on safety and security. This cycle was shaped by a third-party security audit, driving extensive TOCTOU hardening and a sustained, project-wide effort to shrink the amount of unsafe code by removing it outright and migrating low-level syscalls from nix/libc to rustix. On top of that, we landed major zero-copy I/O performance work (splice/tee/pipe), broadened WebAssembly, Cygwin and Windows support, and continued contributing tests and bug reports upstream to GNU coreutils.

---

GNU Test Suite Compatibility:

Result	0.8.0	0.9.0	Change 0.8.0 to 0.9.0	% Total 0.8.0	% Total 0.9.0	% Change 0.8.0 to 0.9.0
Pass	630	625	-5	94.74%	90.58%	-4.16%
Skip	14	8	-6	2.11%	1.16%	-0.95%
Fail	21	56	+35	3.16%	8.12%	+4.96%
Error	0	1	+1	0%	0.14%	+0.14%
Total	665	690	+25 (new tests)

Note: The rise in failing tests is due to the upstream GNU test suite being extended, not to regressions on our side. We updated our GNU reference from 9.10 to 9.11 (PR #11922), which added 25 new tests (665 → 690). Many of these newly-introduced tests are not yet passing, which accounts for the jump from 21 to 56 failures; no previously-passing functionality regressed, and work is ongoing to address the new tests.

---

---

Highlights:

• Security Hardening (Zellic audit)

  • A third-party security audit by Zellic reviewed the codebase; the findings - widely reported as 44 CVEs (see also the Ubuntu update and the corrode write-up Bugs Rust won't catch) - were concentrated in TOCTOU races and filesystem edge cases that Rust's type system does not prevent
  • It's worth noting that many of these CVEs are not memory-safety issues but differences in behavior from GNU coreutils that the audit identified; aligning our semantics with GNU resolves them
  • This release closes many of them: a new TOCTOU-resistant uucore::safe_copy module; TOCTOU fixes in cp, mv, and chmod recursive traversal; rm dot/dotdot path-parsing protection; nohup.out now created with mode 0600; and chroot now resolves all ids before chrooting

• Reducing unsafe & migrating to rustix

  • A sustained, project-wide push to shrink the unsafe surface: dozens of unsafe removals across utilities, tests, fuzz targets and uucore (get_groups, make_fifo, build.rs, and more)
  • Migration from nix/libc to rustix across id, tr, timeout, sort, wc, tail, cp, who, factor, and core process/IO paths

• Performance

  • splice()/tee()/pipe() fast paths landed across cat, wc, head, tail, yes, cp, tee, and unexpand (e.g. unexpand +7.5%, faster cp from a pipe on Linux, tee via raw syscalls, yes using the tee syscall)
  • Consolidated in a reworked uucore::pipes / buf_copy

• GNU Compatibility & Upstream Collaboration

  • Reference bumped to GNU 9.11, which extended the suite with 25 new tests (the reason the failure count went up - see the note above; it is not a regression)
  • We continue to contribute tests and bug reports upstream to GNU coreutils, and our compatibility work keeps surfacing edge cases on both sides
  • New fixes across numfmt, date, tr, cksum, factor, head, stat, and sort

• numfmt Overhaul

  • Precision handling, rejection of scientific notation, LC_NUMERIC decimal separator, zero-padding for negative numbers, IEC precision cap, large %f values, --to=auto exit code, and multi-byte --suffix width accounting

• ls Improvements

  • ls -lF symlink target indicators, link-count column no longer inflated per-ACL-file, version-sorting and recursive-mode fixes, independent permissions-column width

... (truncated)

Commits

• 840c36d shred: fix --remove=unlink with relative paths
• 395d703 stat: fix %N quoting of filenames containing control characters (#12330)
• 89cf583 ls: simplify symlink target indicator logic
• e50a178 tee: restrict to NamedReader
• 55549fa wc: remove a nest by loop{}
• b22013a ls: ls -lF symlink target indicators (#11554)
• 179b977 ln: add WASI support via symlink_path (#11713)
• be80186 sort: fix incorrect sort ordering with long line inputs
• 77bb522 prepare release 0.9.0
• aaf4a35 tee: simplify code
• Additional commits viewable in compare view

Updates uu_arch from 0.8.0 to 0.9.0

Release notes

Sourced from uu_arch's releases.

0.9.0

Rust Coreutils 0.9.0 Release:

We are excited to announce the release of Rust Coreutils 0.9.0 - a release focused on safety and security. This cycle was shaped by a third-party security audit, driving extensive TOCTOU hardening and a sustained, project-wide effort to shrink the amount of unsafe code by removing it outright and migrating low-level syscalls from nix/libc to rustix. On top of that, we landed major zero-copy I/O performance work (splice/tee/pipe), broadened WebAssembly, Cygwin and Windows support, and continued contributing tests and bug reports upstream to GNU coreutils.

---

GNU Test Suite Compatibility:

Result	0.8.0	0.9.0	Change 0.8.0 to 0.9.0	% Total 0.8.0	% Total 0.9.0	% Change 0.8.0 to 0.9.0
Pass	630	625	-5	94.74%	90.58%	-4.16%
Skip	14	8	-6	2.11%	1.16%	-0.95%
Fail	21	56	+35	3.16%	8.12%	+4.96%
Error	0	1	+1	0%	0.14%	+0.14%
Total	665	690	+25 (new tests)

Note: The rise in failing tests is due to the upstream GNU test suite being extended, not to regressions on our side. We updated our GNU reference from 9.10 to 9.11 (PR #11922), which added 25 new tests (665 → 690). Many of these newly-introduced tests are not yet passing, which accounts for the jump from 21 to 56 failures; no previously-passing functionality regressed, and work is ongoing to address the new tests.

---

---

Highlights:

• Security Hardening (Zellic audit)

  • A third-party security audit by Zellic reviewed the codebase; the findings - widely reported as 44 CVEs (see also the Ubuntu update and the corrode write-up Bugs Rust won't catch) - were concentrated in TOCTOU races and filesystem edge cases that Rust's type system does not prevent
  • It's worth noting that many of these CVEs are not memory-safety issues but differences in behavior from GNU coreutils that the audit identified; aligning our semantics with GNU resolves them
  • This release closes many of them: a new TOCTOU-resistant uucore::safe_copy module; TOCTOU fixes in cp, mv, and chmod recursive traversal; rm dot/dotdot path-parsing protection; nohup.out now created with mode 0600; and chroot now resolves all ids before chrooting

• Reducing unsafe & migrating to rustix

  • A sustained, project-wide push to shrink the unsafe surface: dozens of unsafe removals across utilities, tests, fuzz targets and uucore (get_groups, make_fifo, build.rs, and more)
  • Migration from nix/libc to rustix across id, tr, timeout, sort, wc, tail, cp, who, factor, and core process/IO paths

• Performance

  • splice()/tee()/pipe() fast paths landed across cat, wc, head, tail, yes, cp, tee, and unexpand (e.g. unexpand +7.5%, faster cp from a pipe on Linux, tee via raw syscalls, yes using the tee syscall)
  • Consolidated in a reworked uucore::pipes / buf_copy

• GNU Compatibility & Upstream Collaboration

  • Reference bumped to GNU 9.11, which extended the suite with 25 new tests (the reason the failure count went up - see the note above; it is not a regression)
  • We continue to contribute tests and bug reports upstream to GNU coreutils, and our compatibility work keeps surfacing edge cases on both sides
  • New fixes across numfmt, date, tr, cksum, factor, head, stat, and sort

• numfmt Overhaul

  • Precision handling, rejection of scientific notation, LC_NUMERIC decimal separator, zero-padding for negative numbers, IEC precision cap, large %f values, --to=auto exit code, and multi-byte --suffix width accounting

• ls Improvements

  • ls -lF symlink target indicators, link-count column no longer inflated per-ACL-file, version-sorting and recursive-mode fixes, independent permissions-column width

... (truncated)

Commits

• 840c36d shred: fix --remove=unlink with relative paths
• 395d703 stat: fix %N quoting of filenames containing control characters (#12330)
• 89cf583 ls: simplify symlink target indicator logic
• e50a178 tee: restrict to NamedReader
• 55549fa wc: remove a nest by loop{}
• b22013a ls: ls -lF symlink target indicators (#11554)
• 179b977 ln: add WASI support via symlink_path (#11713)
• be80186 sort: fix incorrect sort ordering with long line inputs
• 77bb522 prepare release 0.9.0
• aaf4a35 tee: simplify code
• Additional commits viewable in compare view

Updates uu_base32 from 0.8.0 to 0.9.0

Release notes

Sourced from uu_base32's releases.

0.9.0

Rust Coreutils 0.9.0 Release:

We are excited to announce the release of Rust Coreutils 0.9.0 - a release focused on safety and security. This cycle was shaped by a third-party security audit, driving extensive TOCTOU hardening and a sustained, project-wide effort to shrink the amount of unsafe code by removing it outright and migrating low-level syscalls from nix/libc to rustix. On top of that, we landed major zero-copy I/O performance work (splice/tee/pipe), broadened WebAssembly, Cygwin and Windows support, and continued contributing tests and bug reports upstream to GNU coreutils.

---

GNU Test Suite Compatibility:

Result	0.8.0	0.9.0	Change 0.8.0 to 0.9.0	% Total 0.8.0	% Total 0.9.0	% Change 0.8.0 to 0.9.0
Pass	630	625	-5	94.74%	90.58%	-4.16%
Skip	14	8	-6	2.11%	1.16%	-0.95%
Fail	21	56	+35	3.16%	8.12%	+4.96%
Error	0	1	+1	0%	0.14%	+0.14%
Total	665	690	+25 (new tests)

Note: The rise in failing tests is due to the upstream GNU test suite being extended, not to regressions on our side. We updated our GNU reference from 9.10 to 9.11 (PR #11922), which added 25 new tests (665 → 690). Many of these newly-introduced tests are not yet passing, which accounts for the jump from 21 to 56 failures; no previously-passing functionality regressed, and work is ongoing to address the new tests.

---

---

Highlights:

• Security Hardening (Zellic audit)

  • A third-party security audit by Zellic reviewed the codebase; the findings - widely reported as 44 CVEs (see also the Ubuntu update and the corrode write-up Bugs Rust won't catch) - were concentrated in TOCTOU races and filesystem edge cases that Rust's type system does not prevent
  • It's worth noting that many of these CVEs are not memory-safety issues but differences in behavior from GNU coreutils that the audit identified; aligning our semantics with GNU resolves them
  • This release closes many of them: a new TOCTOU-resistant uucore::safe_copy module; TOCTOU fixes in cp, mv, and chmod recursive traversal; rm dot/dotdot path-parsing protection; nohup.out now created with mode 0600; and chroot now resolves all ids before chrooting

• Reducing unsafe & migrating to rustix

  • A sustained, project-wide push to shrink the unsafe surface: dozens of unsafe removals across utilities, tests, fuzz targets and uucore (get_groups, make_fifo, build.rs, and more)
  • Migration from nix/libc to rustix across id, tr, timeout, sort, wc, tail, cp, who, factor, and core process/IO paths

• Performance

  • splice()/tee()/pipe() fast paths landed across cat, wc, head, tail, yes, cp, tee, and unexpand (e.g. unexpand +7.5%, faster cp from a pipe on Linux, tee via raw syscalls, yes using the tee syscall)
  • Consolidated in a reworked uucore::pipes / buf_copy

• GNU Compatibility & Upstream Collaboration

  • Reference bumped to GNU 9.11, which extended the suite with 25 new tests (the reason the failure count went up - see the note above; it is not a regression)
  • We continue to contribute tests and bug reports upstream to GNU coreutils, and our compatibility work keeps surfacing edge cases on both sides
  • New fixes across numfmt, date, tr, cksum, factor, head, stat, and sort

• numfmt Overhaul

  • Precision handling, rejection of scientific notation, LC_NUMERIC decimal separator, zero-padding for negative numbers, IEC precision cap, large %f values, --to=auto exit code, and multi-byte --suffix width accounting

• ls Improvements

  • ls -lF symlink target indicators, link-count column no longer inflated per-ACL-file, version-sorting and recursive-mode fixes, independent permissions-column width

... (truncated)

Commits

• 840c36d shred: fix --remove=unlink with relative paths
• 395d703 stat: fix %N quoting of filenames containing control characters (#12330)
• 89cf583 ls: simplify symlink target indicator logic
• e50a178 tee: restrict to NamedReader
• 55549fa wc: remove a nest by loop{}
• b22013a ls: ls -lF symlink target indicators (#11554)
• 179b977 ln: add WASI support via symlink_path (#11713)
• be80186 sort: fix incorrect sort ordering with long line inputs
• 77bb522 prepare release 0.9.0
• aaf4a35 tee: simplify code
• Additional commits viewable in compare view

Updates uu_base64 from 0.8.0 to 0.9.0

Release notes

Sourced from uu_base64's releases.

0.9.0

Rust Coreutils 0.9.0 Release:

We are excited to announce the release of Rust Coreutils 0.9.0 - a release focused on safety and security. This cycle was shaped by a third-party security audit, driving extensive TOCTOU hardening and a sustained, project-wide effort to shrink the amount of unsafe code by removing it outright and migrating low-level syscalls from nix/libc to rustix. On top of that, we landed major zero-copy I/O performance work (splice/tee/pipe), broadened WebAssembly, Cygwin and Windows support, and continued contributing tests and bug reports upstream to GNU coreutils.

---

GNU Test Suite Compatibility:

Result	0.8.0	0.9.0	Change 0.8.0 to 0.9.0	% Total 0.8.0	% Total 0.9.0	% Change 0.8.0 to 0.9.0
Pass	630	625	-5	94.74%	90.58%	-4.16%
Skip	14	8	-6	2.11%	1.16%	-0.95%
Fail	21	56	+35	3.16%	8.12%	+4.96%
Error	0	1	+1	0%	0.14%	+0.14%
Total	665	690	+25 (new tests)

Note: The rise in failing tests is due to the upstream GNU test suite being extended, not to regressions on our side. We updated our GNU reference from 9.10 to 9.11 (PR #11922), which added 25 new tests (665 → 690). Many of these newly-introduced tests are not yet passing, which accounts for the jump from 21 to 56 failures; no previously-passing functionality regressed, and work is ongoing to address the new tests.

---

---

Highlights:

• Security Hardening (Zellic audit)

  • A third-party security audit by Zellic reviewed the codebase; the findings - widely reported as 44 CVEs (see also the Ubuntu update and the corrode write-up Bugs Rust won't catch) - were concentrated in TOCTOU races and filesystem edge cases that Rust's type system does not prevent
  • It's worth noting that many of these CVEs are not memory-safety issues but differences in behavior from GNU coreutils that the audit identified; aligning our semantics with GNU resolves them
  • This release closes many of them: a new TOCTOU-resistant uucore::safe_copy module; TOCTOU fixes in cp, mv, and chmod recursive traversal; rm dot/dotdot path-parsing protection; nohup.out now created with mode 0600; and chroot now resolves all ids before chrooting

• Reducing unsafe & migrating to rustix

  • A sustained, project-wide push to shrink the unsafe surface: dozens of unsafe removals across utilities, tests, fuzz targets and uucore (get_groups, make_fifo, build.rs, and more)
  • Migration from nix/libc to rustix across id, tr, timeout, sort, wc, tail, cp, who, factor, and core process/IO paths

• Performance

  • splice()/tee()/pipe() fast paths landed across cat, wc, head, tail, yes, cp, tee, and unexpand (e.g. unexpand +7.5%, faster cp from a pipe on Linux, tee via raw syscalls, yes using the tee syscall)
  • Consolidated in a reworked uucore::pipes / buf_copy

• GNU Compatibility & Upstream Collaboration

  • Reference bumped to GNU 9.11, which extended the suite with 25 new tests (the reason the failure count went up - see the note above; it is not a regression)
  • We continue to contribute tests and bug reports upstream to GNU coreutils, and our compatibility work keeps surfacing edge cases on both sides
  • New fixes across numfmt, date, tr, cksum, factor, head, stat, and sort

• numfmt Overhaul

  • Precision handling, rejection of scientific notation, LC_NUMERIC decimal separator, zero-padding for negative numbers, IEC precision cap, large %f values, --to=auto exit code, and multi-byte --suffix width accounting

• ls Improvements

  • ls -lF symlink target indicators, link-count column no longer inflated per-ACL-file, version-sorting and recursive-mode fixes, independent permissions-column width

... (truncated)

Commits

• 840c36d shred: fix --remove=unlink with relative paths
• 395d703 stat: fix %N quoting of filenames containing control characters (#12330)
• 89cf583 ls: simplify symlink target indicator logic
• e50a178 tee: restrict to NamedReader
• 55549fa wc: remove a nest by loop{}
• b22013a ls: ls -lF symlink target indicators (#11554)
• 179b977 ln: add WASI support via symlink_path (#11713)
• be80186 sort: fix incorrect sort ordering with long line inputs
• 77bb522 prepare release 0.9.0
• aaf4a35 tee: simplify code
• Additional commits viewable in compare view

Updates uu_basename from 0.8.0 to 0.9.0

Release notes

Sourced from uu_basename's releases.

0.9.0

Rust Coreutils 0.9.0 Release:

We are excited to announce the release of Rust Coreutils 0.9.0 - a release focused on safety and security. This cycle was shaped by a third-party security audit, driving extensive TOCTOU hardening and a sustained, project-wide effort to shrink the amount of unsafe code by removing it outright and migrating low-level syscalls from nix/libc to rustix. On top of that, we landed major zero-copy I/O performance work (splice/tee/pipe), broadened WebAssembly, Cygwin and Windows support, and continued contributing tests and bug reports upstream to GNU coreutils.

---

GNU Test Suite Compatibility:

Result	0.8.0	0.9.0	Change 0.8.0 to 0.9.0	% Total 0.8.0	% Total 0.9.0	% Change 0.8.0 to 0.9.0
Pass	630	625	-5	94.74%	90.58%	-4.16%
Skip	14	8	-6	2.11%	1.16%	-0.95%
Fail	21	56	+35	3.16%	8.12%	+4.96%
Error	0	1	+1	0%	0.14%	+0.14%
Total	665	690	+25 (new tests)

Note: The rise in failing tests is due to the upstream GNU test suite being extended, not to regressions on our side. We updated our GNU reference from 9.10 to 9.11 (PR #11922), which added 25 new tests (665 → 690). Many of these newly-introduced tests are not yet passing, which accounts for the jump from 21 to 56 failures; no previously-passing functionality regressed, and work is ongoing to address the new tests.

---

---

Highlights:

• Security Hardening (Zellic audit)

  • A third-party security audit by Zellic reviewed the codebase; the findings - widely reported as 44 CVEs (see also the Ubuntu update and the corrode write-up Bugs Rust won't catch) - were concentrated in TOCTOU races and filesystem edge cases that Rust's type system does not prevent
  • It's worth noting that many of these CVEs are not memory-safety issues but differences in behavior from GNU coreutils that the audit identified; aligning our semantics with GNU resolves them
  • This release closes many of them: a new TOCTOU-resistant uucore::safe_copy module; TOCTOU fixes in cp, mv, and chmod recursive traversal; rm dot/dotdot path-parsing protection; nohup.out now created with mode 0600; and chroot now resolves all ids before chrooting

• Reducing unsafe & migrating to rustix

  • A sustained, project-wide push to shrink the unsafe surface: dozens of unsafe removals across utilities, tests, fuzz targets and uucore (get_groups, make_fifo, build.rs, and more)
  • Migration from nix/libc to Description has been truncated

[github-actions]

Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 294e84a.

♻️ This comment has been updated with latest results.