| commit | a1bbf1dae1ca1968364093b31b2a7e388d10877f | [log] [tgz] |
|---|---|---|
| author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Mon Oct 06 16:52:47 2025 -0400 |
| committer | GitHub <noreply@github.com> | Mon Oct 06 16:52:47 2025 -0400 |
| tree | 7c8c26bd724011daeaa50a45e948db8f2934a0fe | |
| parent | 07ccc526b1e7a2ce191afc3c8d0d6f34dec4f9f5 [diff] |
Bump anyio from 4.10.0 to 4.11.0 in /tools (#6044) Bumps [anyio](https://github.com/agronholm/anyio) from 4.10.0 to 4.11.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/agronholm/anyio/releases">anyio's releases</a>.</em></p> <blockquote> <h2>4.11.0</h2> <ul> <li>Added support for cancellation reasons (the <code>reason</code> parameter to <code>CancelScope.cancel()</code>) (<a href="https://redirect.github.com/agronholm/anyio/pull/975">#975</a>)</li> <li>Bumped the minimum version of Trio to v0.31.0</li> <li>Added the ability to enter the event loop from foreign (non-worker) threads by passing the return value of <code>anyio.lowlevel.current_token()</code> to <code>anyio.from_thread.run()</code> and <code>anyio.from_thread.run_sync()</code> as the <code>token</code> keyword argument (<a href="https://redirect.github.com/agronholm/anyio/issues/256">#256</a>)</li> <li>Added pytest option (<code>anyio_mode = "auto"</code>) to make the pytest plugin automatically handle all async tests (<a href="https://redirect.github.com/agronholm/anyio/pull/971">#971</a>)</li> <li>Added the <code>anyio.Condition.wait_for()</code> method for feature parity with asyncio (<a href="https://redirect.github.com/agronholm/anyio/pull/974">#974</a>)</li> <li>Changed the default type argument of <code>anyio.abc.TaskStatus</code> from <code>Any</code> to <code>None</code> (<a href="https://redirect.github.com/agronholm/anyio/pull/964">#964</a>)</li> <li>Fixed TCP listener behavior to guarantee the same ephemeral port is used for all socket listeners when <code>local_port=0</code> (<a href="https://redirect.github.com/agronholm/anyio/issues/857">#857</a>; PR by <a href="https://github.com/11kkw"><code>@11kkw</code></a> and <a href="https://github.com/agronholm"><code>@agronholm</code></a>)</li> <li>Fixed inconsistency between Trio and asyncio where a TCP stream that previously raised a <code>BrokenResourceError</code> on <code>send()</code> would still raise <code>BrokenResourceError</code> after the stream was closed on asyncio, but <code>ClosedResourceError</code> on Trio. They now both raise a <code>ClosedResourceError</code> in this scenario. (<a href="https://redirect.github.com/agronholm/anyio/issues/671">#671</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/agronholm/anyio/blob/master/docs/versionhistory.rst">anyio's changelog</a>.</em></p> <blockquote> <h1>Version history</h1> <p>This library adheres to <code>Semantic Versioning 2.0 <http://semver.org/></code>_.</p> <p><strong>4.11.0</strong></p> <ul> <li>Added support for cancellation reasons (the <code>reason</code> parameter to <code>CancelScope.cancel()</code>) (<code>[#975](https://github.com/agronholm/anyio/issues/975) <https://github.com/agronholm/anyio/pull/975></code>_)</li> <li>Bumped the minimum version of Trio to v0.31.0</li> <li>Added the ability to enter the event loop from foreign (non-worker) threads by passing the return value of <code>anyio.lowlevel.current_token()</code> to <code>anyio.from_thread.run()</code> and <code>anyio.from_thread.run_sync()</code> as the <code>token</code> keyword argument (<code>[#256](https://github.com/agronholm/anyio/issues/256) <https://github.com/agronholm/anyio/issues/256></code>_)</li> <li>Added pytest option (<code>anyio_mode = "auto"</code>) to make the pytest plugin automatically handle all async tests (<code>[#971](https://github.com/agronholm/anyio/issues/971) <https://github.com/agronholm/anyio/pull/971></code>_)</li> <li>Added the <code>anyio.Condition.wait_for()</code> method for feature parity with asyncio (<code>[#974](https://github.com/agronholm/anyio/issues/974) <https://github.com/agronholm/anyio/pull/974></code>_)</li> <li>Changed the default type argument of <code>anyio.abc.TaskStatus</code> from <code>Any</code> to <code>None</code> (<code>[#964](https://github.com/agronholm/anyio/issues/964) <https://github.com/agronholm/anyio/pull/964></code>_)</li> <li>Fixed TCP listener behavior to guarantee the same ephemeral port is used for all socket listeners when <code>local_port=0</code> (<code>[#857](https://github.com/agronholm/anyio/issues/857) <https://github.com/agronholm/anyio/issues/857></code>_; PR by <a href="https://github.com/11kkw"><code>@11kkw</code></a> and <a href="https://github.com/agronholm"><code>@agronholm</code></a>)</li> <li>Fixed inconsistency between Trio and asyncio where a TCP stream that previously raised a <code>BrokenResourceError</code> on <code>send()</code> would still raise <code>BrokenResourceError</code> after the stream was closed on asyncio, but <code>ClosedResourceError</code> on Trio. They now both raise a <code>ClosedResourceError</code> in this scenario. (<code>[#671](https://github.com/agronholm/anyio/issues/671) <https://github.com/agronholm/anyio/issues/671></code>_)</li> </ul> <p><strong>4.10.0</strong></p> <ul> <li> <p>Added the <code>feed_data()</code> method to the <code>BufferedByteReceiveStream</code> class, allowing users to inject data directly into the buffer</p> </li> <li> <p>Added various class methods to wrap existing sockets as listeners or socket streams:</p> <ul> <li><code>SocketListener.from_socket()</code></li> <li><code>SocketStream.from_socket()</code></li> <li><code>UNIXSocketStream.from_socket()</code></li> <li><code>UDPSocket.from_socket()</code></li> <li><code>ConnectedUDPSocket.from_socket()</code></li> <li><code>UNIXDatagramSocket.from_socket()</code></li> <li><code>ConnectedUNIXDatagramSocket.from_socket()</code></li> </ul> </li> <li> <p>Added a hierarchy of connectable stream classes for transparently connecting to various remote or local endpoints for exchanging bytes or objects</p> </li> <li> <p>Added context manager mix-in classes (<code>anyio.ContextManagerMixin</code> and <code>anyio.AsyncContextManagerMixin</code>) to help write classes that embed other context managers, particularly cancel scopes or task groups (<code>[#905](https://github.com/agronholm/anyio/issues/905) <https://github.com/agronholm/anyio/pull/905></code>_; PR by <a href="https://github.com/agronholm"><code>@agronholm</code></a> and</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/agronholm/anyio/commit/08737af202f6610cdb8ba53fecaefd9c03269637"><code>08737af</code></a> Bumped up the version</li> <li><a href="https://github.com/agronholm/anyio/commit/8bb9fe04a1c0a4b6615c843d4a88bba38a386059"><code>8bb9fe0</code></a> Fixed the inconsistent exception on sending to a closed TCP stream (<a href="https://redirect.github.com/agronholm/anyio/issues/980">#980</a>)</li> <li><a href="https://github.com/agronholm/anyio/commit/963709358a05ced66986e928b593b4bd82422981"><code>9637093</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/agronholm/anyio/issues/981">#981</a>)</li> <li><a href="https://github.com/agronholm/anyio/commit/f1bc6ee95a75007681ef9cb4eec0369838b390e9"><code>f1bc6ee</code></a> Fixed changelog entry formatting</li> <li><a href="https://github.com/agronholm/anyio/commit/0b58964a26c68ca427b711bbe8536f61ed900133"><code>0b58964</code></a> Mentioned the sub-interpreter support in the README</li> <li><a href="https://github.com/agronholm/anyio/commit/1ed112c65628d3cce312e7b6875b9f914d174a71"><code>1ed112c</code></a> Ensure same port is used for IPv4/IPv6 when creating TCP listener with local_...</li> <li><a href="https://github.com/agronholm/anyio/commit/aceeee09868642311a96626924f2f09c088a26c0"><code>aceeee0</code></a> Re-enabled coverage reporting on macOS</li> <li><a href="https://github.com/agronholm/anyio/commit/6b890dc869f54b6237caff52a74e86382c076ad2"><code>6b890dc</code></a> Reworded a changelog entry and added PR links to others</li> <li><a href="https://github.com/agronholm/anyio/commit/944257d2d59e8057dd00cd5cc96d8f73028031dd"><code>944257d</code></a> Updated pre-commit modules</li> <li><a href="https://github.com/agronholm/anyio/commit/087975f44599471a84bea2077731143a346c276a"><code>087975f</code></a> Fixed a documentation style (<a href="https://redirect.github.com/agronholm/anyio/issues/976">#976</a>)</li> <li>Additional commits viewable in <a href="https://github.com/agronholm/anyio/compare/4.10.0...4.11.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The Bazel Central Registry (BCR) is the default registry for Bazel's external dependency system (“Bzlmod”). This is the GitHub repository backing the contents of the BCR, hosted at https://bcr.bazel.build/. For the website that allows you to search modules and see their versions conveniently, visit https://registry.bazel.build/.
Besides hosting metadata about Bazel-specific libraries (commonly known as “rulesets”), the BCR is also a central host for projects that don't have upstream support for Bazel (most commonly, C/C++ projects).
The BCR is just like a regular Bazel registry, with some extra metadata fields and policy restrictions. You can contribute to the BCR by sending pull requests; see BCR policies and contribution guidelines for more information.
The core infrastructure of the Bazel Central Registry depends on GitHub and Google Cloud. Bazel users who enable Bzlmod (the default since Bazel 8) depend on the BCR by default. While we try to keep the BCR infrastructure simple and reliable, we assume no liability for any damages caused by build failures due to potential BCR infrastructure failures.
If you consider it necessary, you can do the following to avoid depending on the BCR infrastructure while still making use of the information checked into the BCR.
--registry is a flag that can be specified multiple times.--registry flag is specified, the BCR is the only registry Bazel consults.--registry flag is specified, Bazel will consult the specified registries in order, but will not consult the BCR unless the BCR is explicitly specified as a registry. In other words, to use your own registry layered on top of the BCR, use --registry=https://my.own.registry.com/ --registry=https://bcr.bazel.build/../bazel_registry.json. You can run bazel run //tools:print_all_src_urls to get the list of source URLs to mirror for all Bazel modules checked into the BCR. For example, https://foo.com/bar.zip should be mirrored to https://<your mirror>/foo.com/bar.zip.