[PR #1321] [CLOSED] Bump async-std from 1.7.0 to 1.8.0 #2205

New issue

Closed

opened 2026-03-16 07:25:34 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 07:25:34 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/1321
Author: @dependabot-preview[bot]
Created: 12/14/2020
Status: ❌ Closed

Base: main ← Head: dependabot/cargo/async-std-1.8.0

📝 Commits (1)

401a2d3 Bump async-std from 1.7.0 to 1.8.0

📊 Changes

2 files changed (+6 additions, -5 deletions)

View changed files

📝 Cargo.lock (+4 -3)
📝 crates/async-std-resolver/Cargo.toml (+2 -2)

📄 Description

Bumps async-std from 1.7.0 to 1.8.0.

Release notes

Sourced from async-std's releases.

v1.8.0

This patch introduces async_std::channel, a new submodule for our async channels implementation. channels have been one of async-std's most requested features, and have existed as "unstable" for the past year. We've been cautious about stabilizing channels, and this caution turned out to be warranted: we realized our channels could hang indefinitely under certain circumstances, and people ended up expressing a need for unbounded channels.

So today we're introducing the new async_std::channel submodule which exports the async-channel crate, and we're marking the older unstable async_std::sync::channel API as "deprecated". This release includes both APIs, but we intend to stabilize async_std::channel and remove the older API in January. This should give dependent projects a month to upgrade, though we can extend that if it proves to be too short.

The rationale for adding a new top-level channel submodule, rather than extending sync is that the std::sync and async_std::sync submodule are a bit of a mess, and the libs team has been talking about splitting std::sync up into separate modules. The stdlib has to guarantee it'll forever be backwards compatible, but async-std does not (we fully expect a 2.0 once we have async closures & traits). So we're experimenting with this change before std does, with the expectation that this change can serve as a data point when the libs team decides how to proceed in std.

Added

async_std::channel as "unstable" #915

async_std::process as "unstable" #916

Fixed

Fixed mentions of the tokio03 flags in the docs #909

Fixed a double drop issue in StreamExt::cycle #903

Internal

updated pin-project to v0.2.0

Changelog

Sourced from async-std's changelog.

[1.8.0] - 2020-12-04

This patch introduces async_std::channel, a new submodule for our async channels implementation. channels have been one of async-std's most requested features, and have existed as "unstable" for the past year. We've been cautious about stabilizing channels, and this caution turned out to be warranted: we realized our channels could hang indefinitely under certain circumstances, and people ended up expressing a need for unbounded channels.

So today we're introducing the new async_std::channel submodule which exports the async-channel crate, and we're marking the older unstable async_std::sync::channel API as "deprecated". This release includes both APIs, but we intend to stabilize async_std::channel and remove the older API in January. This should give dependent projects a month to upgrade, though we can extend that if it proves to be too short.

The rationale for adding a new top-level channel submodule, rather than extending sync is that the std::sync and async_std::sync submodule are a bit of a mess, and the libs team has been talking about splitting std::sync up into separate modules. The stdlib has to guarantee it'll forever be backwards compatible, but async-std does not (we fully expect a 2.0 once we have async closures & traits). So we're experimenting with this change before std does, with the expectation that this change can serve as a data point when the libs team decides how to proceed in std.

Added

async_std::channel as "unstable" #915

async_std::process as "unstable" #916

Fixed

Fixed mentions of the tokio03 flags in the docs #909

Fixed a double drop issue in StreamExt::cycle #903

Internal

updated pin-project to v0.2.0

Commits

fde2f58 Merge pull request #917 from async-rs/v1.8.0
c738d73 v1.8.0
2757969 Merge pull request #918 from async-rs/restore-prior-process-exports
34e9ff3 Restore sync process exports
9cd0578 Merge pull request #916 from async-rs/async-process
f8f1eac Attempt 2 at fixing docs on windows
92f5038 attempt to fix docs builds
415d0d1 Merge pull request #732 from hhggit/timeout_repeat
6ae69c9 Merge pull request #915 from async-rs/feat-new-channels
151025f fixup
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 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)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
@dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

Update frequency (including time of day and day of week)
Pull request limits (per update run and/or open at any time)
Automerge options (never/patch/minor, and dev/runtime dependencies)
Out-of-range updates (receive only lockfile updates, if desired)
Security updates (receive only security updates, if desired)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/1321 **Author:** [@dependabot-preview[bot]](https://github.com/apps/dependabot-preview) **Created:** 12/14/2020 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/cargo/async-std-1.8.0` --- ### 📝 Commits (1) - [`401a2d3`](https://github.com/hickory-dns/hickory-dns/commit/401a2d3d7797a6af187d92527fa4e865f801071b) Bump async-std from 1.7.0 to 1.8.0 ### 📊 Changes **2 files changed** (+6 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+4 -3) 📝 `crates/async-std-resolver/Cargo.toml` (+2 -2) </details> ### 📄 Description Bumps [async-std](https://github.com/async-rs/async-std) from 1.7.0 to 1.8.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/async-rs/async-std/releases">async-std's releases</a>.</em></p> <blockquote> <h2>v1.8.0</h2> <p>This patch introduces <code>async_std::channel</code>, a new submodule for our async channels implementation. <code>channels</code> have been one of async-std's most requested features, and have existed as "unstable" for the past year. We've been cautious about stabilizing channels, and this caution turned out to be warranted: we realized our channels could hang indefinitely under certain circumstances, and people ended up expressing a need for unbounded channels.</p> <p>So today we're introducing the new <code>async_std::channel</code> submodule which exports the <code>async-channel</code> crate, and we're marking the older unstable <code>async_std::sync::channel</code> API as "deprecated". This release includes both APIs, but we intend to stabilize <code>async_std::channel</code> and remove the older API in January. This should give dependent projects a month to upgrade, though we can extend that if it proves to be too short.</p> <p>The rationale for adding a new top-level <code>channel</code> submodule, rather than extending <code>sync</code> is that the <code>std::sync</code> and <code>async_std::sync</code> submodule are a bit of a mess, and the libs team <a href="%5Bhttps://github-redirect.dependabot.com/rust-lang/rfcs/pull/2788#discussion_r339092478%5D(https://github-redirect.dependabot.com/rust-lang/rfcs/pull/2788#discussion_r339092478)">has been talking about splitting <code>std::sync</code> up</a> into separate modules. The stdlib has to guarantee it'll forever be backwards compatible, but <code>async-std</code> does not (we fully expect a 2.0 once we have async closures & traits). So we're experimenting with this change before <code>std</code> does, with the expectation that this change can serve as a data point when the libs team decides how to proceed in std.</p> <h3>Added</h3> <ul> <li><code>async_std::channel</code> as "unstable" <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/915">#915</a></li> <li><code>async_std::process</code> as "unstable" <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/916">#916</a></li> </ul> <h3>Fixed</h3> <ul> <li>Fixed mentions of the <code>tokio03</code> flags in the docs <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/909">#909</a></li> <li>Fixed a double drop issue in <code>StreamExt::cycle</code> <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/903">#903</a></li> </ul> <h3>Internal</h3> <ul> <li>updated <code>pin-project</code> to <code>v0.2.0</code></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/async-rs/async-std/blob/master/CHANGELOG.md">async-std's changelog</a>.</em></p> <blockquote> <h1>[1.8.0] - 2020-12-04</h1> <p>This patch introduces <code>async_std::channel</code>, a new submodule for our async channels implementation. <code>channels</code> have been one of async-std's most requested features, and have existed as "unstable" for the past year. We've been cautious about stabilizing channels, and this caution turned out to be warranted: we realized our channels could hang indefinitely under certain circumstances, and people ended up expressing a need for unbounded channels.</p> <p>So today we're introducing the new <code>async_std::channel</code> submodule which exports the <code>async-channel</code> crate, and we're marking the older unstable <code>async_std::sync::channel</code> API as "deprecated". This release includes both APIs, but we intend to stabilize <code>async_std::channel</code> and remove the older API in January. This should give dependent projects a month to upgrade, though we can extend that if it proves to be too short.</p> <p>The rationale for adding a new top-level <code>channel</code> submodule, rather than extending <code>sync</code> is that the <code>std::sync</code> and <code>async_std::sync</code> submodule are a bit of a mess, and the libs team <a href="%5Bhttps://github-redirect.dependabot.com/rust-lang/rfcs/pull/2788#discussion_r339092478%5D(https://github-redirect.dependabot.com/rust-lang/rfcs/pull/2788#discussion_r339092478)">has been talking about splitting <code>std::sync</code> up</a> into separate modules. The stdlib has to guarantee it'll forever be backwards compatible, but <code>async-std</code> does not (we fully expect a 2.0 once we have async closures & traits). So we're experimenting with this change before <code>std</code> does, with the expectation that this change can serve as a data point when the libs team decides how to proceed in std.</p> <h3>Added</h3> <ul> <li><code>async_std::channel</code> as "unstable" <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/915">#915</a></li> <li><code>async_std::process</code> as "unstable" <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/916">#916</a></li> </ul> <h3>Fixed</h3> <ul> <li>Fixed mentions of the <code>tokio03</code> flags in the docs <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/909">#909</a></li> <li>Fixed a double drop issue in <code>StreamExt::cycle</code> <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/903">#903</a></li> </ul> <h3>Internal</h3> <ul> <li>updated <code>pin-project</code> to <code>v0.2.0</code></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/async-rs/async-std/commit/fde2f58610ad8ddc1d7729d1cf6ca5e870f98ac3"><code>fde2f58</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/917">#917</a> from async-rs/v1.8.0</li> <li><a href="https://github.com/async-rs/async-std/commit/c738d73bd7a6ac465580135d59556528f01747d7"><code>c738d73</code></a> v1.8.0</li> <li><a href="https://github.com/async-rs/async-std/commit/2757969f5d03a2b92b6a405074fbc820b4041009"><code>2757969</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/918">#918</a> from async-rs/restore-prior-process-exports</li> <li><a href="https://github.com/async-rs/async-std/commit/34e9ff3cd2aab8971a5e0338b2afbcb1725f8b7d"><code>34e9ff3</code></a> Restore sync process exports</li> <li><a href="https://github.com/async-rs/async-std/commit/9cd0578826372e453497ab9b56edf618c794cae3"><code>9cd0578</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/916">#916</a> from async-rs/async-process</li> <li><a href="https://github.com/async-rs/async-std/commit/f8f1eacc9aa8b32a0987b1dd436fd6974d57dc4b"><code>f8f1eac</code></a> Attempt 2 at fixing docs on windows</li> <li><a href="https://github.com/async-rs/async-std/commit/92f5038ed658ac75e7788cadacccaac7dda4430b"><code>92f5038</code></a> attempt to fix docs builds</li> <li><a href="https://github.com/async-rs/async-std/commit/415d0d1e517b5862f7fd7a78513adad40a111571"><code>415d0d1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/732">#732</a> from hhggit/timeout_repeat</li> <li><a href="https://github.com/async-rs/async-std/commit/6ae69c94d2f855f8ba1533f77d05cf46adbb3a10"><code>6ae69c9</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/async-rs/async-std/issues/915">#915</a> from async-rs/feat-new-channels</li> <li><a href="https://github.com/async-rs/async-std/commit/151025fa38c98eb519053f7d151054e8f7b14f91"><code>151025f</code></a> fixup</li> <li>Additional commits viewable in <a href="https://github.com/async-rs/async-std/compare/v1.7.0...v1.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=async-std&package-manager=cargo&previous-version=1.7.0&new-version=1.8.0)](https://dependabot.com/compatibility-score/?dependency-name=async-std&package-manager=cargo&previous-version=1.7.0&new-version=1.8.0) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>