build(deps): bump tokio from 1.43.0 to 1.44.2

[dependabot[bot]]

Bumps tokio from 1.43.0 to 1.44.2.

Release notes

Sourced from tokio's releases.

Tokio v1.44.2

This release fixes a soundness issue in the broadcast channel. The channel accepts values that are Send but !Sync. Previously, the channel called clone() on these values without synchronizing. This release fixes the channel by synchronizing calls to .clone() (Thanks Austin Bonander for finding and reporting the issue).

Fixed

• sync: synchronize clone() call in broadcast channel (#7232)

#7232: tokio-rs/tokio#7232

Tokio v1.44.1

1.44.1 (March 13th, 2025)

Fixed

• rt: skip defer queue in block_in_place context (#7216)

#7216: tokio-rs/tokio#7216

Tokio v1.44.0

1.44.0 (March 7th, 2025)

This release changes the from_std method on sockets to panic if a blocking socket is provided. We determined this change is not a breaking change as Tokio is not intended to operate using blocking sockets. Doing so results in runtime hangs and should be considered a bug. Accidentally passing a blocking socket to Tokio is one of the most common user mistakes. If this change causes an issue for you, please comment on #7172.

Added

• coop: add task::coop module (#7116)
• process: add Command::get_kill_on_drop() (#7086)
• sync: add broadcast::Sender::closed (#6685, #7090)
• sync: add broadcast::WeakSender (#7100)
• sync: add oneshot::Receiver::is_empty() (#7153)
• sync: add oneshot::Receiver::is_terminated() (#7152)

Fixed

• fs: empty reads on File should not start a background read (#7139)
• process: calling start_kill on exited child should not fail (#7160)
• signal: fix CTRL_CLOSE, CTRL_LOGOFF, CTRL_SHUTDOWN on windows (#7122)
• sync: properly handle panic during mpsc drop (#7094)

Changes

• runtime: clean up magic number in registration set (#7112)
• coop: make coop yield using waker defer strategy (#7185)
• macros: make select! budget-aware (#7164)
• net: panic when passing a blocking socket to from_std (#7166)
• io: clean up buffer casts (#7142)

... (truncated)

Commits

• ec4b1d7 chore: forward port 1.43.x
• e3c3a56 Merge branch 'tokio-1.43.x' into forward-port-1.43.x
• a7b658c chore: prepare Tokio v1.43.1 release
• c1c8d10 Merge remote-tracking branch 'origin/tokio-1.38.x' into forward-port-1.38.x
• aa303bc chore: prepare Tokio v1.38.2 release
• 7b6ccb5 chore: backport CI fixes
• 4b174ce sync: fix cloning value when receiving from broadcast channel
• d413c9c chore: prepare Tokio v1.44.1 (#7217)
• addbfb9 rt: skip defer queue in block_in_place context (#7216)
• 8182ecf chore: prepare Tokio v1.44.0 (#7202)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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) You can disable automated security fix PRs for this repo from the Security Alerts page.