dependabot[bot] opened a new pull request, #67: URL: https://github.com/apache/solr-orbit/pull/67
Updates the requirements on [numpy](https://github.com/numpy/numpy), [coverage](https://github.com/coveragepy/coveragepy) and [ruff](https://github.com/astral-sh/ruff) to permit the latest version. Updates `numpy` to 2.5.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/numpy/numpy/releases";>numpy's releases</a>.</em></p> <blockquote> <h2>v2.5.2 (Aug 9, 2026)</h2> <h1>NumPy 2.5.2 Release Notes</h1> <p>The NumPy 2.5.2 is a patch release that fixes bugs discovered after the 2.5.1 release. The big news is that it includes wheels for the newly released Python 3.15.0rc1.</p> <p>This release supports Python versions 3.12-3.15</p> <h2>C API changes</h2> <h3><code>PyArray_StringDTypeObject</code> is opaque under the abi3t stable ABI</h3> <p>The <code>PyArray_StringDTypeObject</code> was accidentally exposed in NumPy 2.5 when targeting the free-threading-compatible stable ABI (<code>Py_TARGET_ABI3T</code>). <code>PyArray_StringDTypeObject</code> is now an opaque struct: extensions compiled that way cannot access its fields, since the struct layout depends on the size of the object header. Any code that accessed <code>PyArray_StringDTypeObject</code> fields in an abi3t build would have crashed, so we are making this API change in a bugfix release.</p> <p>The <code>NpyString</code> allocator API remains usable by passing the descriptor object pointer, e.g. <code>NpyString_acquire_allocator((PyArray_StringDTypeObject *)descr)</code>.</p> <p>(<a href="https://redirect.github.com/numpy/numpy/pull/31771";>gh-31771</a>)</p> <h2>Contributors</h2> <p>A total of 16 people contributed to this release. People with a "+" by their names contributed a patch for the first time.</p> <ul> <li>Abhijeetsingh Meena +</li> <li>Charalampos Stratakis</li> <li>Charles Harris</li> <li>Chris Ninham +</li> <li>David Woods</li> <li>Geonho +</li> <li>Gopu Yeshwanth Reddy +</li> <li>Iason Krommydas</li> <li>Ijtihed Kilani</li> <li>Jelle Zijlstra +</li> <li>Joren Hammudoglu</li> <li>Kumar Aditya</li> <li>Mike Boyle</li> <li>Nathan Goldbaum</li> <li>Raghuveer Devulapalli</li> <li>Sebastian Berg</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst";>numpy's changelog</a>.</em></p> <blockquote> <p>This is a walkthrough of the NumPy 2.4.0 release on Linux, which will be the first feature release using the <code>numpy/numpy-release <https://github.com/numpy/numpy-release></code>__ repository.</p> <p>The commands can be copied into the command line, but be sure to replace 2.4.0 with the correct version. This should be read together with the :ref:<code>general release guide <prepare_release></code>.</p> <h1>Facility preparation</h1> <p>Before beginning to make a release, use the <code>requirements/*_requirements.txt</code> files to ensure that you have the needed software. Most software can be installed with pip, but some will require apt-get, dnf, or whatever your system uses for software. You will also need a GitHub personal access token (PAT) to push the documentation. There are a few ways to streamline things:</p> <ul> <li>Git can be set up to use a keyring to store your GitHub personal access token. Search online for the details.</li> </ul> <h1>Prior to release</h1> <h2>Add/drop Python versions</h2> <p>When adding or dropping Python versions, multiple config and CI files need to be edited in addition to changing the minimum version in <code>pyproject.toml</code>. Make these changes in an ordinary PR against main and backport if necessary. We currently release wheels for new Python versions after the first Python RC once manylinux and cibuildwheel support that new Python version.</p> <h2>Backport pull requests</h2> <p>Changes that have been marked for this release must be backported to the maintenance/2.4.x branch.</p> <h2>Update 2.4.0 milestones</h2> <p>Look at the issues/prs with 2.4.0 milestones and either push them off to a later version, or maybe remove the milestone. You may need to add a milestone.</p> <h2>Check the numpy-release repo</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/numpy/numpy/commit/48fecee5453aa1d31e6b79dcb3969dc1a6d1a891";><code>48fecee</code></a> REL: Prepare for the NumPy 2.5.2 release (<a href="https://redirect.github.com/numpy/numpy/issues/32226";>#32226</a>)</li> <li><a href="https://github.com/numpy/numpy/commit/ecf599ce3995e07be7298d226cbcce34b31a1f0a";><code>ecf599c</code></a> Merge pull request <a href="https://redirect.github.com/numpy/numpy/issues/32221";>#32221</a> from charris/backport-32151</li> <li><a href="https://github.com/numpy/numpy/commit/3c7ac97a576ef0ec22ce5aa1b924724942124d59";><code>3c7ac97</code></a> Merge pull request <a href="https://redirect.github.com/numpy/numpy/issues/32220";>#32220</a> from charris/backport-32205</li> <li><a href="https://github.com/numpy/numpy/commit/23b30f49b390ffa504364886717d75cf22789b74";><code>23b30f4</code></a> BUG: avoid segfaults when legacy copyswap slot is not defined (<a href="https://redirect.github.com/numpy/numpy/issues/32151";>#32151</a>)</li> <li><a href="https://github.com/numpy/numpy/commit/4964ca8930f3a2ca8da14399c5ea68a6f3fc088b";><code>4964ca8</code></a> TYP: <code>isclose</code> shape-typing fix for 2d array-likes (<a href="https://redirect.github.com/numpy/numpy/issues/32205";>#32205</a>)</li> <li><a href="https://github.com/numpy/numpy/commit/c37ed944dcb27b4e0320972f2b5a5a5a07737c53";><code>c37ed94</code></a> MAINT: Skip limited_api tests on some platforms. (<a href="https://redirect.github.com/numpy/numpy/issues/32214";>#32214</a>)</li> <li><a href="https://github.com/numpy/numpy/commit/5cfd73b6f0114592724aa90ebebbf091ffb775f1";><code>5cfd73b</code></a> Merge pull request <a href="https://redirect.github.com/numpy/numpy/issues/32206";>#32206</a> from charris/update-cibuildwheel</li> <li><a href="https://github.com/numpy/numpy/commit/d8262bcae74ad393a2a65cf50f36eb9f402aeeec";><code>d8262bc</code></a> MAINT: Update cibuildwheel to v4.2.0</li> <li><a href="https://github.com/numpy/numpy/commit/988d94d8cf4e3bfbff59107ee177543eed024be1";><code>988d94d</code></a> Merge pull request <a href="https://redirect.github.com/numpy/numpy/issues/32158";>#32158</a> from charris/backport-32133</li> <li><a href="https://github.com/numpy/numpy/commit/b2e4f97f15635817791aa12832a90c5a1347b821";><code>b2e4f97</code></a> BUG: avoid possible stack overflow in arraydescr_dealloc (<a href="https://redirect.github.com/numpy/numpy/issues/32133";>#32133</a>)</li> <li>Additional commits viewable in <a href="https://github.com/numpy/numpy/compare/v1.24.2...v2.5.2";>compare view</a></li> </ul> </details> <br /> Updates `coverage` from 7.15.2 to 7.16.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/coveragepy/coveragepy/releases";>coverage's releases</a>.</em></p> <blockquote> <h2>7.16.0</h2> <h2>Version 7.16.0 — 2026-08-28</h2> <ul> <li>When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define <code>[paths]</code> configuration to combine data across operating systems. Fixes <a href="https://redirect.github.com/coveragepy/coveragepy/issues/2266";>issue 2266</a>.</li> <li>The <a href="https://coverage.readthedocs.io/en/latest/api_coverage.html#coverage.Coverage.switch_context";>Coverage.switch_context()</a> method now returns the previous context.</li> <li>Fix: previously, a <code>[paths]</code> pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2268";>pull 2268</a>.</li> <li>Fixes to validation of options and configuration settings: <ul> <li>Negative precision settings now always cause useful error messages (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2261";>pull 2261</a>).</li> <li>An invalid regex in the <code>--contexts</code> option (or the <code>[report] contexts</code> setting) reported a confusing “Couldn’t use data file …: user-defined function raised exception” error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2262";>pull 2262</a>).</li> <li>Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren’t strings (like <code>omit</code>, <code>exclude_lines</code>, or a <code>[paths]</code> entry), file settings like <code>data_file</code>, and any wrong-typed value in the <code>[paths]</code> section (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2263";>pull 2263</a>).</li> <li><code>coverage run</code> refuses run-affecting command-line options like <code>--branch</code> alongside <code>--concurrency=multiprocessing</code>, since they can’t reach the subprocesses. The check only recognized <code>multiprocessing</code> as the entire option value, so <code>--concurrency=multiprocessing,thread</code> slipped through and failed later with “Can’t combine statement coverage data with branch data”. Each named concurrency library is now properly considered (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2270";>pull 2270</a>).</li> </ul> </li> <li>Fix: <code>coverage annotate -d DIR</code> raised an <code>AssertionError</code> if any measured file had an extension other than <code>.py</code>, such as a <code>.pyw</code> file on Windows. The original extension is now restored on the annotated copy (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2265";>pull 2265</a>).</li> </ul> <p>:arrow_right: PyPI page: <a href="https://pypi.org/project/coverage/7.16.0";>coverage 7.16.0</a>. :arrow_right: To install: <code>python3 -m pip install coverage==7.16.0</code></p> <h2>7.15.4</h2> <h2>Version 7.15.4 — 2026-08-06</h2> <ul> <li>Fix: in the HTML report, a source file name containing a double quote (legal on POSIX) wasn’t escaped where it’s dropped into the <code>href</code> of the index and prev/next links, so it could close the attribute early and inject markup. Page URLs are now escaped. Thanks, <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2227";>Rajath Mohare</a>.</li> <li>Fix: the LCOV report wrote file names and other fields into its line-oriented records without neutralizing control characters. A measured file whose name contained a newline (legal on POSIX) could forge extra records, inflating the coverage seen by tools that read the report. Control characters in a field are now replaced. Thanks, <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2226";>Rajath Mohare</a>.</li> <li>Wheels are now provided for Python 3.15.</li> </ul> <p>:arrow_right: PyPI page: <a href="https://pypi.org/project/coverage/7.15.4";>coverage 7.15.4</a>. :arrow_right: To install: <code>python3 -m pip install coverage==7.15.4</code></p> <h2>7.15.3</h2> <h2>Version 7.15.3 — 2026-08-02</h2> <ul> <li>Fix: the sysmon core is incompatible with dynamic contexts. Previously, the combination would be prevented when read from the coverage.py configuration. But using the context API as pytest-cov does, contexts would be silently dropped. Now a warning is issued, thanks to <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2234";>Jisang Han</a>. Closes <a href="https://redirect.github.com/coveragepy/coveragepy/issues/2200";>issue 2200</a>.</li> <li>A performance improvement in the low-level line number bookkeeping when combining data files, thanks to <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2239";>Kevin Turcios</a>.</li> <li>Performance improvement in HTML reporting by reducing the number of times files have to be parsed, thanks to <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2240";>Kevin Turcios</a>.</li> </ul> <p>:arrow_right: PyPI page: <a href="https://pypi.org/project/coverage/7.15.3";>coverage 7.15.3</a>. :arrow_right: To install: <code>python3 -m pip install coverage==7.15.3</code></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/coveragepy/coveragepy/blob/main/CHANGES.rst";>coverage's changelog</a>.</em></p> <blockquote> <h2>Version 7.16.0 — 2026-08-28</h2> <ul> <li> <p>When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define <code>[paths]</code> configuration to combine data across operating systems. Fixes <code>issue 2266</code>_.</p> </li> <li> <p>The :meth:<code>.Coverage.switch_context</code> method now returns the previous context.</p> </li> <li> <p>Fix: previously, a <code>[paths]</code> pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in <code>pull 2268</code>_.</p> </li> <li> <p>Fixes to validation of options and configuration settings:</p> <ul> <li> <p>Negative precision settings now always cause useful error messages (<code>pull 2261</code>_).</p> </li> <li> <p>An invalid regex in the <code>--contexts</code> option (or the <code>[report] contexts</code> setting) reported a confusing "Couldn't use data file ...: user-defined function raised exception" error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (<code>pull 2262</code>_).</p> </li> <li> <p>Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren't strings (like <code>omit</code>, <code>exclude_lines</code>, or a <code>[paths]</code> entry), file settings like <code>data_file</code>, and any wrong-typed value in the <code>[paths]</code> section (<code>pull 2263</code>_).</p> </li> <li> <p><code>coverage run</code> refuses run-affecting command-line options like <code>--branch</code> alongside <code>--concurrency=multiprocessing</code>, since they can't reach the subprocesses. The check only recognized <code>multiprocessing</code> as the entire option value, so <code>--concurrency=multiprocessing,thread</code> slipped through and failed later with "Can't combine statement coverage data with branch data". Each named concurrency library is now properly considered (<code>pull 2270</code>_).</p> </li> </ul> </li> <li> <p>Fix: <code>coverage annotate -d DIR</code> raised an <code>AssertionError</code> if any measured file had an extension other than <code>.py</code>, such as a <code>.pyw</code> file on Windows. The original extension is now restored on the annotated copy (<code>pull 2265</code>_).</p> </li> </ul> <p>.. _pull 2261: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2261";>coveragepy/coveragepy#2261</a> .. _pull 2262: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2262";>coveragepy/coveragepy#2262</a> .. _pull 2263: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2263";>coveragepy/coveragepy#2263</a> .. _pull 2265: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2265";>coveragepy/coveragepy#2265</a> .. _issue 2266: <a href="https://redirect.github.com/coveragepy/coveragepy/issues/2266";>coveragepy/coveragepy#2266</a> .. _pull 2268: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2268";>coveragepy/coveragepy#2268</a></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/coveragepy/coveragepy/commit/3e9fc1653ef31089d02eb7618b9d9ac9414378fc";><code>3e9fc16</code></a> docs: prep for 7.16.0</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/38be8d13afee6b6525492fc375c739cdfb675e9b";><code>38be8d1</code></a> build: control check-manifest explicitly</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/8eb1266ead5c6d356d3437637a509ff86b566253";><code>8eb1266</code></a> docs(build): no longer commit sample_html</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/1a8b3fa57d56bb70bad62c93d224c18a0fbaae6f";><code>1a8b3fa</code></a> docs: remove sample_html</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/aeaa79b812d1bc637ebb5582ab12c076e192c87e";><code>aeaa79b</code></a> docs: linklint is now sphinx-linklint</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/d5eaf3f6d38f58746bc69e87e64c0b0277a9077d";><code>d5eaf3f</code></a> test: a branchless way to re-add extensions</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/57e52fd431cecc1ca03de2c5b1288e0b330c2ef4";><code>57e52fd</code></a> docs: adjust CHANGES for <a href="https://redirect.github.com/coveragepy/coveragepy/issues/2270";>#2270</a></li> <li><a href="https://github.com/coveragepy/coveragepy/commit/b9d304d77f7ce3d55df3a46339dbc56d1f49df58";><code>b9d304d</code></a> fix: check for multiprocessing in a --concurrency list (<a href="https://redirect.github.com/coveragepy/coveragepy/issues/2270";>#2270</a>)</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/a6ef9284afbc7d1f392821864b64ddbda0051fc5";><code>a6ef928</code></a> chore: make upgrade</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/070461fcfde0437b5b778c2c2a72e433a0a391aa";><code>070461f</code></a> chore: bump the action-dependencies group with 4 updates (<a href="https://redirect.github.com/coveragepy/coveragepy/issues/2271";>#2271</a>)</li> <li>Additional commits viewable in <a href="https://github.com/coveragepy/coveragepy/compare/7.15.2...7.16.0";>compare view</a></li> </ul> </details> <br /> Updates `ruff` from 0.16.0 to 0.16.5 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/ruff/releases";>ruff's releases</a>.</em></p> <blockquote> <h2>0.16.5</h2> <h2>Release Notes</h2> <p>Released on 2026-08-27.</p> <h3>Preview features</h3> <ul> <li>Allow rules without codes (<a href="https://redirect.github.com/astral-sh/ruff/pull/28049";>#28049</a>)</li> <li>Introduce category selectors (<a href="https://redirect.github.com/astral-sh/ruff/pull/27666";>#27666</a>)</li> <li>Update preview default rules and categories (<a href="https://redirect.github.com/astral-sh/ruff/pull/27877";>#27877</a>)</li> </ul> <h3>Bug fixes</h3> <ul> <li>[<code>flake8-async</code>] Detect blocking generic HTTP requests (<code>ASYNC210</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/28024";>#28024</a>)</li> <li>[<code>flake8-datetimez</code>] Allow timezone-safe <code>strptime</code> chains (<code>DTZ007</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/28023";>#28023</a>)</li> <li>[<code>flake8-simplify</code>] Respect side effects in <code>lambda</code> defaults (<code>SIM401</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/28000";>#28000</a>)</li> </ul> <h3>Server</h3> <ul> <li>Fix duplicated "of" in <code>ClientOptions</code> doc comment (<a href="https://redirect.github.com/astral-sh/ruff/pull/27978";>#27978</a>)</li> </ul> <h3>Documentation</h3> <ul> <li>Document rule acceptance guidelines (<a href="https://redirect.github.com/astral-sh/ruff/pull/27910";>#27910</a>)</li> <li>Document the new category selectors (<a href="https://redirect.github.com/astral-sh/ruff/pull/27906";>#27906</a>)</li> </ul> <h3>Contributors</h3> <ul> <li><a href="https://github.com/AlexWaygood";><code>@AlexWaygood</code></a></li> <li><a href="https://github.com/sharkdp";><code>@sharkdp</code></a></li> <li><a href="https://github.com/jelle-openai";><code>@jelle-openai</code></a></li> <li><a href="https://github.com/charliermarsh";><code>@charliermarsh</code></a></li> <li><a href="https://github.com/ntBre";><code>@ntBre</code></a></li> <li><a href="https://github.com/aarushkandukoori";><code>@aarushkandukoori</code></a></li> </ul> <h2>Install ruff 0.16.5</h2> <h3>Install prebuilt binaries via shell script</h3> <pre lang="sh"><code>curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ruff/releases/download/0.16.5/ruff-installer.sh | sh </code></pre> <h3>Install prebuilt binaries via powershell script</h3> <pre lang="sh"><code>powershell -ExecutionPolicy Bypass -c "irm https://releases.astral.sh/github/ruff/releases/download/0.16.5/ruff-installer.ps1 | iex" </code></pre> <h2>Download ruff 0.16.5</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md";>ruff's changelog</a>.</em></p> <blockquote> <h2>0.16.5</h2> <p>Released on 2026-08-27.</p> <h3>Preview features</h3> <ul> <li>Allow rules without codes (<a href="https://redirect.github.com/astral-sh/ruff/pull/28049";>#28049</a>)</li> <li>Introduce category selectors (<a href="https://redirect.github.com/astral-sh/ruff/pull/27666";>#27666</a>)</li> <li>Update preview default rules and categories (<a href="https://redirect.github.com/astral-sh/ruff/pull/27877";>#27877</a>)</li> </ul> <h3>Bug fixes</h3> <ul> <li>[<code>flake8-async</code>] Detect blocking generic HTTP requests (<code>ASYNC210</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/28024";>#28024</a>)</li> <li>[<code>flake8-datetimez</code>] Allow timezone-safe <code>strptime</code> chains (<code>DTZ007</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/28023";>#28023</a>)</li> <li>[<code>flake8-simplify</code>] Respect side effects in <code>lambda</code> defaults (<code>SIM401</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/28000";>#28000</a>)</li> </ul> <h3>Server</h3> <ul> <li>Fix duplicated "of" in <code>ClientOptions</code> doc comment (<a href="https://redirect.github.com/astral-sh/ruff/pull/27978";>#27978</a>)</li> </ul> <h3>Documentation</h3> <ul> <li>Document rule acceptance guidelines (<a href="https://redirect.github.com/astral-sh/ruff/pull/27910";>#27910</a>)</li> <li>Document the new category selectors (<a href="https://redirect.github.com/astral-sh/ruff/pull/27906";>#27906</a>)</li> </ul> <h3>Contributors</h3> <ul> <li><a href="https://github.com/AlexWaygood";><code>@AlexWaygood</code></a></li> <li><a href="https://github.com/sharkdp";><code>@sharkdp</code></a></li> <li><a href="https://github.com/jelle-openai";><code>@jelle-openai</code></a></li> <li><a href="https://github.com/charliermarsh";><code>@charliermarsh</code></a></li> <li><a href="https://github.com/ntBre";><code>@ntBre</code></a></li> <li><a href="https://github.com/aarushkandukoori";><code>@aarushkandukoori</code></a></li> </ul> <h2>0.16.4</h2> <p>Released on 2026-08-20.</p> <h3>Preview features</h3> <ul> <li>[<code>flake8-use-pathlib</code>] Add autofix for <code>PTH116</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/26460";>#26460</a>)</li> <li>[<code>refurb</code>] Restrict <code>delete-full-slice</code> to lists (<code>FURB131</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/27711";>#27711</a>)</li> <li>[<code>refurb</code>] Skip <code>FURB101</code> and <code>FURB103</code> when the <code>open</code> argument is a file descriptor (<a href="https://redirect.github.com/astral-sh/ruff/pull/27643";>#27643</a>)</li> </ul> <h3>Bug fixes</h3> <ul> <li>Fix <code>InvalidInstruction</code> on Windows CPUs that do not support <code>POPCNT</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/27803";>#27803</a>)</li> <li>[<code>pyflakes</code>] Emit semantic syntax errors in string type definitions as <code>F722</code> (<a href="https://redirect.github.com/astral-sh/ruff/pull/27835";>#27835</a>)</li> <li>[<code>pylint</code>] Allow <code>os._exit</code> imports in <code>import-private-name</code> (<code>PLC2701</code>) (<a href="https://redirect.github.com/astral-sh/ruff/pull/27738";>#27738</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/ruff/commit/9e4938c4a60bed3e87a11ee1e1db1bd23f4d964a";><code>9e4938c</code></a> Bump 0.16.5 (<a href="https://redirect.github.com/astral-sh/ruff/issues/28110";>#28110</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/aad0e909ef1390f4b2a3ba8aa0a67fb8ea5cbacd";><code>aad0e90</code></a> Allow rules without codes (<a href="https://redirect.github.com/astral-sh/ruff/issues/28049";>#28049</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/5fdab73c5052350400c36b08c5d7710210343bc4";><code>5fdab73</code></a> Update preview default rules and categories (<a href="https://redirect.github.com/astral-sh/ruff/issues/27877";>#27877</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/29c8e5b2d0a46eb7dc4ff11c1b0a0dc5ccea52e4";><code>29c8e5b</code></a> Document rule acceptance guidelines (<a href="https://redirect.github.com/astral-sh/ruff/issues/27910";>#27910</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/50a4d7fd106603a5616b01ac3bef3306252b248f";><code>50a4d7f</code></a> Document the new category selectors (<a href="https://redirect.github.com/astral-sh/ruff/issues/27906";>#27906</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/ada87950ea188f882f69b7bd6e2213a9696e3ee2";><code>ada8795</code></a> Introduce category selectors (<a href="https://redirect.github.com/astral-sh/ruff/issues/27666";>#27666</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/d8947238863b61922bfc83f07edcc697c1cc07c0";><code>d894723</code></a> [ty] Infer lambda parameters through callable type aliases (<a href="https://redirect.github.com/astral-sh/ruff/issues/28109";>#28109</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/2685fdebbcf9938736fed8c45886a629f9c99a06";><code>2685fde</code></a> [ty] Narrow functional enum members in <code>==</code> and <code>match</code> (<a href="https://redirect.github.com/astral-sh/ruff/issues/28103";>#28103</a>)</li> <li><a href="https://github.com/astral-sh/ruff/commit/efcffd2178ce62e9951a53d4c50cadc225a0cfec";><code>efcffd2</code></a> [ty] Intersection simplifications with subtype-related generic specialization...</li> <li><a href="https://github.com/astral-sh/ruff/commit/eb780488037504e11f145ed778654fd8a825028b";><code>eb78048</code></a> [ty] Bump ecosystem-analyzer for HTML escaping (<a href="https://redirect.github.com/astral-sh/ruff/issues/28104";>#28104</a>)</li> <li>Additional commits viewable in <a href="https://github.com/astral-sh/ruff/compare/0.16.0...0.16.5";>compare view</a></li> </ul> </details> <br /> 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 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 </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
