chore(deps): bump libc from 0.2.186 to 0.2.189 in /crates/atlas-cersei

[dependabot]

Bumps libc from 0.2.186 to 0.2.189.

Release notes

Sourced from libc's releases.

0.2.189

Added

• Emscripten: Add pthread_sigmask, sigwait, sigwaitinfo, sigtimedwait, faccessat, and pthread_kill (#5270)
• Linux SPARC: Enable the clone3 syscall (#4980)
• Solarish: Add CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID (#5274)

Deprecated

• Deprecate CLONE_INTO_CGROUP and CLONE_CLEAR_SIGHAND. These overflow their types and will be changed to a larger size in the future. (8c6e6710458d)

Fixed

• Musl riscv32: Rename padding fields to avoid a conflict and fix the build (2499ff0ad993)
• NuttX: Fix wchar_t definition under Arm (#5245)
• Windows: Add back link names for time-related symbols (#5300)

0.2.188

Changed

• Restore Send and Sync for DIR (35b062263401)

These were removed in 0.2.187 because libc does not actually make Send and Sync guarantees 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: Send or libc::DIR: Sync.

0.2.187

This release contains a number of improvements related to 64-bit time_t configuration. Of note the existing RUST_LIBC_UNSTABLE_* environment variables have been replaced with configuration options. The new way to use these is:

RUSTFLAGS='--cfg=libc_unstable_musl_v1_2_3' cargo ...
RUSTFLAGS='--cfg=libc_unstable_gnu_time_bits="64"' cargo ...

Being able to set this via RUSTFLAGS makes it easier to only apply configuration to specific targets (and notably, not the host if build scripts are used).

There are two other notable changes:

• The 32-bit windows-gnu targets now respect libc_unstable_gnu_time_bits

• uClibc now supports a similar configuration option:

  RUSTFLAGS='--cfg=libc_unstable_uclibc_time64'

... (truncated)

Changelog

Sourced from libc's changelog.

0.2.189 - 2026-07-21

Added

• Emscripten: Add pthread_sigmask, sigwait, sigwaitinfo, sigtimedwait, faccessat, and pthread_kill (#5270)
• Linux SPARC: Enable the clone3 syscall (#4980)
• Solarish: Add CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID (#5274)

Deprecated

• Deprecate CLONE_INTO_CGROUP and CLONE_CLEAR_SIGHAND. These overflow their types and will be changed to a larger size in the future. (8c6e6710458d)

Fixed

• Musl riscv32: Rename padding fields to avoid a conflict and fix the build (2499ff0ad993)
• NuttX: Fix wchar_t definition under Arm (#5245)
• Windows: Add back link names for time-related symbols (#5300)

0.2.188 - 2026-07-21

Changed

• Restore Send and Sync for DIR (35b062263401)

These were removed in 0.2.187 because libc does not actually make Send and Sync guarantees 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: Send or libc::DIR: Sync.

0.2.187 - 2026-07-20

This release contains a number of improvements related to 64-bit time_t configuration. Of note the existing RUST_LIBC_UNSTABLE_* environment variables have been replaced with configuration options. The new way to use these is:

RUSTFLAGS='--cfg=libc_unstable_musl_v1_2_3' cargo ...
RUSTFLAGS='--cfg=libc_unstable_gnu_time_bits="64"' cargo ...

Being able to set this via RUSTFLAGS makes it easier to only apply configuration to specific targets (and notably, not the host if build scripts are used).

There are two other notable changes:

• The 32-bit windows-gnu targets now respect libc_unstable_gnu_time_bits
• uClibc now supports a similar configuration option:

... (truncated)

Commits

• ef0906e libc: Release 0.2.189
• 5a79f76 riscv32-musl: Rename padding fields to avoid a conflict
• 3e51062 psp: Fix overflowing_literals warnings
• e352fdd emscripten: add pthread_sigmask, sigwait, sigwaitinfo, sigtimedwait, faccessa...
• 63221b3 macros: Require safe in safe_f! invocations
• 707ab52 macros: Require unsafe in f! invocations
• 8e40c94 Enable clone3() syscall on sparc-linux and sparc64-linux
• 8427909 windows: Add back link names for time-related symbols
• b4863fa nuttx: fix wchar_t definition under arm
• 41c683d nuttx: mirror type definitions
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[uzayer]

Closing in favour of the regrouped Dependabot config merged in #145.

This PR is one of 36 opened by the 2026-08-10 run, 23 of which were five shared dependencies replayed once per crate — crates/* are standalone packages with their own Cargo.lock, so Dependabot saw them as unrelated projects. #145 collapses the 16 Cargo entries into one using directories with a glob, and adds group-by: dependency-name so a dependency is one PR across every crate that uses it.

Nothing here was rejected on its merits — CI was green. The reason not to merge it is the conflict fan-out: five of these PRs touch src-tauri/Cargo.lock and eight crates have three apiece, so landing them individually means each merge conflicts the rest, and every auto-rebase fires a fresh 17-job CI run. Grouped, the same updates arrive as roughly 13 PRs with versions consistent across crates.

Caveat worth recording: closing unmerged may mark these exact versions as dismissed, in which case they return on the next release of each dependency rather than immediately. For patch bumps of this kind that is a matter of weeks, and the grouped form is worth the wait.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.