chore(deps): bump hyper-util, system-configuration, lru, aws-sdk, and others

[jdx]

Summary

• hyper-util 0.1.19 → 0.1.20
• system-configuration 0.6.1 → 0.7.0
• lru 0.12.5 → 0.16.3
• aws-sdk-s3 1.119.0 → 1.121.0
• arc-swap 1.8.0 → 1.8.1
• aws-smithy-eventstream 0.60.17 → 0.60.18
• aws-smithy-query 0.60.12 → 0.60.13
• insta 1.46.2 → 1.46.3
• mockito 1.7.1 → 1.7.2
• schemars 1.2.0 → 1.2.1
• zmij 1.0.18 → 1.0.19

Fixes panic in macOS sandboxes (e.g., Claude Code) where SCDynamicStore::create returns NULL during proxy detection.

Closes #7909

Test plan

• cargo check passes
• All pre-commit lints pass
• CI passes

🤖 Generated with Claude Code

---

Note

Medium Risk
Lockfile-only dependency upgrades touch networking/AWS client and macOS system configuration stacks, which can subtly change runtime behavior despite no application code changes.

Overview
Bumps key dependencies via Cargo.lock, notably aws-sdk-s3 (and a set of aws-smithy-* crates), hyper-util, system-configuration, and lru.

These updates also pull in several transitive changes (e.g., new aws-smithy-http/spin versions and Windows-related crate bumps), altering the resolved dependency graph without changing application source.

^{Written by Cursor Bugbot for commit 036bd45. This will update automatically on new commits. Configure here.}

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Summary of Changes

Hello @jdx, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on updating several core Rust dependencies to their newer versions. The most significant impact of these updates is the resolution of a critical panic issue observed in macOS sandboxed environments, which was caused by an older version of the system-configuration crate. These dependency bumps ensure the project benefits from the latest features, bug fixes, and security improvements provided by these upstream libraries.

Highlights

• Dependency Updates: Several key dependencies have been bumped to their latest versions, including hyper-util, system-configuration, lru, and aws-sdk-s3 along with its related aws-smithy crates.
• macOS Sandbox Fix: The update to system-configuration specifically addresses and fixes a panic that occurred in macOS sandboxed environments (e.g., Claude Code) when SCDynamicStore::create returned NULL during proxy detection.

Changelog

• Cargo.lock
  • Updated hyper-util from 0.1.19 to 0.1.20.
  • Updated system-configuration from 0.6.1 to 0.7.0, addressing a macOS sandbox panic.
  • Updated lru from 0.12.5 to 0.16.3.
  • Updated aws-sdk-s3 from 1.119.0 to 1.121.0, and several related aws-smithy crates including aws-smithy-async (1.2.10 -> 1.2.11), aws-smithy-checksums (0.63.12 -> 0.63.13), aws-smithy-http-client (1.1.8 -> 1.1.9), aws-smithy-observability (0.2.3 -> 0.2.4), aws-smithy-runtime (1.9.8 -> 1.10.0), aws-smithy-runtime-api (1.11.2 -> 1.11.3), and aws-smithy-types (1.4.2 -> 1.4.3).
  • The aws-smithy-http package was updated to 0.63.3, and its version references within other aws-smithy dependencies were adjusted.
  • Updated itertools from 0.10.5 to 0.13.0 across multiple dependencies.
  • Updated windows-sys from 0.59.0 to 0.61.2 in several packages, and to 0.60.2 in socket2's build-dependencies.
  • Updated crc-fast from 1.6.0 to 1.9.0, which now depends on spin 0.10.0 and removes rand and regex.
  • Updated socket2 from 0.5.10 to 0.6.2.
  • Updated hashbrown from 0.15.5 to 0.16.1, which also removed allocator-api2 and equivalent dependencies.
  • The spin package was updated from 0.9.8 to 0.10.0. Notably, parking_lot_core's dependency on spin was explicitly pinned to 0.9.8, while crc-fast now depends on the newer spin 0.10.0.
  • Added http-body-util as a dependency for aws-smithy-runtime-api.

Activity

• The author has confirmed that cargo check passes.
• All pre-commit lints have passed successfully.
• CI is expected to pass, indicating the changes are stable.
• The pull request was generated using Claude Code.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates several dependencies, notably hyper-util, system-configuration, lru, and aws-sdk-* crates. The primary goal of fixing a panic on macOS related to proxy detection seems to be correctly addressed by the bump of system-configuration. The dependency updates are reasonable. One minor concern is the introduction of a second version of the aws-smithy-http crate, which increases dependency complexity. I've added a specific comment about this. Overall, this is a good and necessary update.

[gemini-code-assist]

This pull request introduces a second version of the aws-smithy-http crate into the dependency tree (0.62.6 and 0.63.3). This is likely a result of updating some aws-sdk-* crates while others remain on older versions with different aws-smithy-http requirements.

While having duplicate versions of crates is not a critical issue, it does increase the final binary size and overall dependency complexity. It would be beneficial to investigate if all aws-sdk-* dependencies can be updated to versions that rely on a single version of aws-smithy-http in a future PR to maintain better dependency hygiene.

[github-actions]

Hyperfine Performance

mise x -- echo

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.1 x -- echo	20.2 ± 0.4	19.5	24.6	1.00
mise x -- echo	20.6 ± 0.3	19.9	22.4	1.02 ± 0.03

mise env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.1 env	19.7 ± 0.5	19.0	24.0	1.00
mise env	20.0 ± 0.5	19.4	22.4	1.02 ± 0.04

mise hook-env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.1 hook-env	20.4 ± 0.3	19.9	21.4	1.00
mise hook-env	20.8 ± 0.3	20.1	21.9	1.02 ± 0.02

mise ls

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.2.1 ls	18.4 ± 0.3	17.9	19.4	1.00
mise ls	18.7 ± 0.4	18.1	22.3	1.02 ± 0.03

xtasks/test/perf

Command	mise-2026.2.1	mise	Variance
install (cached)	112ms	112ms	+0%
ls (cached)	70ms	70ms	+0%
bin-paths (cached)	74ms	74ms	+0%
task-ls (cached)	545ms	⚠️ 2490ms	-78%

⚠️ Warning: task-ls cached performance variance is -78%