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

[dependabot]

Bumps the cargo group with 4 updates in the / directory: git2, time, wasmtime and aws-sdk-sso.

Updates git2 from 0.20.2 to 0.20.4

Changelog

Sourced from git2's changelog.

0.20.4 - 2026-02-02

0.20.3...0.20.4

Fixed

• Fix undefined behavior when dereferencing empty Buf. #1213

0.20.3 - 2025-12-06

0.20.2...0.20.3

Changed

• Bumped requirement to libgit2-sys 0.18.3, which updates libgit2 from 1.9.0 to 1.9.2. #1197

Commits

• 8852d7d Merge pull request #1214 from weihanglo/backport-from-raw-parts
• 0b274f7 Bump to 0.20.4
• 73a5d5d Add test for dereference of an empty Buf
• ce56683 fix: check ptr nullity before calling from_raw_parts
• 7cf345c Merge pull request #1197 from ehuss/git2-0.20-br
• dd41077 Bump git2 to 0.20.3
• a6a58e2 Merge pull request #1195 from ehuss/update-libgit2
• See full diff in compare view

Updates time from 0.3.44 to 0.3.47

Release notes

Sourced from time's releases.

v0.3.47

See the changelog for details.

v0.3.46

See the changelog for details.

v0.3.45

See the changelog for details.

Changelog

Sourced from time's changelog.

0.3.47 [2026-02-05]

Security

• The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now, the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable limit.

  This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format.

Compatibility

• Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will error at compile time if the type being formatted does not provide sufficient information. This would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is only configured for parsing (i.e. Iso8601::PARSING) will error at compile time.

Added

• Builder methods for format description modifiers, eliminating the need for verbose initialization when done manually.
• date!(2026-W01-2) is now supported. Previously, a space was required between W and 01.
• [end] now has a trailing_input modifier which can either be prohibit (the default) or discard. When it is discard, all remaining input is ignored. Note that if there are components after [end], they will still attempt to be parsed, likely resulting in an error.

Changed

• More performance gains when parsing.

Fixed

• If manually formatting a value, the number of bytes written was one short for some components. This has been fixed such that the number of bytes written is always correct.
• The possibility of integer overflow when parsing an owned format description has been effectively eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the depth as u8, it is stored as u32. This would require multiple gigabytes of nested input to overflow, at which point we've got other problems and trivial mitigations are available by downstream users.

0.3.46 [2026-01-23]

Added

• All possible panics are now documented for the relevant methods.
• The need to use #[serde(default)] when using custom serde formats is documented. This applies only when deserializing an Option<T>.
• Duration::nanoseconds_i128 has been made public, mirroring std::time::Duration::from_nanos_u128.

... (truncated)

Commits

• d5144cd v0.3.47 release
• f6206b0 Guard against integer overflow in release mode
• 1c63dc7 Avoid denial of service when parsing Rfc2822
• 5940df6 Add builder methods to avoid verbose construction
• 00881a4 Manually format macros everywhere
• bb723b6 Add trailing_input modifier to end
• 31c4f8e Permit W12 in date! macro
• 490a17b Mark error paths in well-known formats as cold
• 6cb1896 Optimize Rfc2822 parsing
• 6d264d5 Remove erroneous #[inline(never)] attributes
• Additional commits viewable in compare view

Updates wasmtime from 33.0.2 to 36.0.5

Release notes

Sourced from wasmtime's releases.

v36.0.5

36.0.5

Released 2026-01-26.

Fixed

• Fixed a bug in lowering of f64.copysign on x86-64 whereby when combined with an f64.load, the resulting machine code could read 16 bytes rather than 8 bytes. This could result in a segfault when Wasmtime is configured without signals-based traps.

v36.0.4

36.0.4

Released 2026-01-14.

Fixed

• A possible stack overflow in the x64 backend with cmp emission has been fixed. #12333

v36.0.3

36.0.3

Released 2025-11-11.

Fixed

• Prevent using shared memories with Memory. CVE-2025-64345

v36.0.2

36.0.2

Released 2025-08-26.

Fixed

• Wasmtime will no longer panic in the pooling allocator when in near-OOM conditions related to resetting the linear memory of a slot. #11510

v36.0.1

36.0.1

Released 2025-08-21.

Added

... (truncated)

Changelog

Sourced from wasmtime's changelog.

36.0.5

Released 2026-01-26.

Fixed

• Fixed a bug in lowering of f64.copysign on x86-64 whereby when combined with an f64.load, the resulting machine code could read 16 bytes rather than 8 bytes. This could result in a segfault when Wasmtime is configured without signals-based traps.

---

36.0.4

Released 2026-01-14.

Fixed

• A possible stack overflow in the x64 backend with cmp emission has been fixed. #12333

---

36.0.3

Released 2025-11-11.

Fixed

• Prevent using shared memories with Memory. CVE-2025-64345

---

36.0.2

Released 2025-08-26.

Fixed

• Wasmtime will no longer panic in the pooling allocator when in near-OOM conditions related to resetting the linear memory of a slot. #11510

---

36.0.1

... (truncated)

Commits

• 06ef143 Release Wasmtime 36.0.5 (#12432)
• ac92d9b [36.0] Backport Cranelift: x64: fix incorrect load-sinking in copysign oper...
• 0489f91 Release Wasmtime 36.0.4 (#12348)
• 5c1a5f6 Cranelift: x64: fix user-controlled recursion in cmp emission. (#12333) (#12338)
• 8c97ae8 Migrate this workspace to using trusted publishing (#12257) (#12280)
• 17d037f Release Wasmtime 36.0.3 (#12023)
• 9fe3f5f [36.0.x] Prevent using shared memories with Memory (#12018)
• f554fa9 [36.0.x] Use github immutable releases (#11916)
• 1578779 Allow dead code in component_api fuzz target (#11575) (#11844)
• be3cc21 Rename doc_auto_cfg to doc_cfg (#11809)
• Additional commits viewable in compare view

Updates aws-sdk-sso from 1.88.0 to 1.90.0

Commits

• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.