Bug 1990382 - chore: upgrade chrono 0.4.41 → 0.4.42, windows-link 0.1.1 → 0.2.1 r=#supply-chain-reviewers

Some common dependencies are starting to consume `windows-link` 0.2,
like `backtrace` with
<rust-lang/backtrace-rs#727>. This is going to
become increasingly common, as crates previously targeting
`windows-target` and `windows-sys` realize they can use `windows-link`
for the small set of Windows platform APIs they actually need.

This is the shortest path to start consuming `windows-link` 0.2, and
I think it turned out to be pretty easy to review!

Differential Revision: https://phabricator.services.mozilla.com/D265914

Author: ErichDonGubler

Cargo.lock

@@ -1332,6 +1332,11 @@ criteria = "safe-to-deploy"
 delta = "0.4.19 -> 0.4.40"
 notes = "Significant refactor of both implementation and dependencies."
 
+[[audits.chrono]]
+who = "Erich Gubler <[email protected]>"
+criteria = "safe-to-deploy"
+delta = "0.4.41 -> 0.4.42"
+
 [[audits.chunked_transfer]]
 who = "Glenn Watson <[email protected]>"
 criteria = "safe-to-deploy"
@@ -7119,6 +7124,11 @@ criteria = "safe-to-deploy"
 version = "0.1.1"
 notes = "A microsoft crate allowing unsafe calls to windows apis."
 
+[[audits.windows-link]]
+who = "Erich Gubler <[email protected]>"
+criteria = "safe-to-deploy"
+delta = "0.1.1 -> 0.2.0"
+
 [[audits.winreg]]
 who = "Ray Kraesig <[email protected]>"
 criteria = "safe-to-run"

supply-chain/audits.toml

@@ -922,6 +922,13 @@ user-id = 64539
 user-login = "kennykerr"
 user-name = "Kenny Kerr"
 
+[[publisher.windows-link]]
+version = "0.2.1"
+when = "2025-10-06"
+user-id = 64539
+user-login = "kennykerr"
+user-name = "Kenny Kerr"
+
 [[publisher.windows-result]]
 version = "0.2.0"
 when = "2024-07-03"