[pull] master from aio-libs:master #344
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [zstandard](https://github.com/indygreg/python-zstandard) from 0.24.0 to 0.25.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/indygreg/python-zstandard/releases">zstandard's releases</a>.</em></p> <blockquote> <h2>0.25.0</h2> <ul> <li>PyO3 Rust created upgraded from 0.24 to 0.25. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/273">#273</a>)</li> <li>We now use <code>Py_REFCNT(obj)</code> instead of accessing <code>(*obj)->ob_refcnt</code> directly. This fixes a nogil / multi-threaded compile error. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/201">#201</a>, <a href="https://redirect.github.com/indygreg/python-zstandard/issues/275">#275</a>)</li> <li>A zstandard commit to fix qsort detection on BSD operating systems has been backported. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/272">#272</a>)</li> <li>The <code>PYTHON_ZSTANDARD_IMPORT_POLICY</code> environment variable now has leading and trailing whitespace stripped. Values like <code> cffi</code> and <code>cffi </code> are now equivalent to <code>cffi</code>.</li> <li>The CI jobs for building wheels have been overhauled to always use <code>cibuildwheel</code> and <code>uv</code> (where possible). This change should be backwards compatible. But wheel building for this project has historically been fragile and there may be unwanted changes. We're optimistic that standardizing on uv (except for musllinux ppc64le and s390x where uv isn't available) will lead to more stability over time.</li> <li>CI now runs tests against the wheels we distribute. Previously, we ran tests against a separate build that was theoretically identical. But the builds may have been subtly different, leading to preventable bugs in our wheels. (Enabling this test coverage did not uncover any failures.)</li> <li>The <code>pyproject.toml</code> build backend has been switched from <code>setuptools.build_meta:__legacy__</code> to <code>setuptools.build_meta</code>.</li> <li>The setuptools build dependency has been upgraded from <69.0.0 to >=77.0.0. Modern versions of setuptools broke <code>--config-settings=--build-option=...</code> as part of implementing PEP 660. A workaround is to use <code>--config-settings=--global-option=...</code> instead. <code>--global-option</code> apparently is deprecated and the setuptools folks have yet to figure out how to thread config settings into <code>setup.py</code> invocations. (<code>--build-option</code> is sent to the <code>build_wheel</code> command but not the <code>build_editable</code> command.)</li> <li>Python 3.14 wheels are now built with <code>manylinux_2_28</code> (versus <code>manylinux2014</code>) for older Python versions. This may raise the minimum glibc version, effectively dropping support for Debian 8 and 9, Ubuntu 13.10 through 18.04, Fedora 19 to 28, and RHEL/Centos 7. However, in practice most platforms don't container newer glibc symbols and are still ABI compatible with <code>manylinux2014</code> and glibc 2.17.</li> <li>We now require cffi >= 2.0.0b on Python 3.14. <3.14 still requires 1.17. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/274">#274</a>)</li> <li>The cffi backend is now automatically disabled for free-threaded builds on Python <3.14, as cffi didn't implement free-threaded support until the 2.0 release. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/274">#274</a>)</li> <li>Added CI coverage for free-threaded CPython 3.13 and 3.14. We do not yet formally support free-threaded builds. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/276">#276</a>)</li> <li>The C and Rust backends now declare the GIL as unused.</li> <li>The <code>pythoncapi_compat.h</code> file has been upgraded to the latest version. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/278">#278</a>)</li> <li><code>setup.py</code> now depends on <code>packaging</code> and uses <code>packaging.version.Version</code> for version comparisons. This removes some deprecation warnings from usage of legacy distutils <code>Version</code> classes.</li> <li>Relax run-time libzstd version checking in C extension from exactly 1.5.7 to >=1.5.6. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/254">#254</a>, <a href="https://redirect.github.com/indygreg/python-zstandard/issues/267">#267</a>)</li> <li>C extension types now (correctly) declare their fully qualified type names</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/indygreg/python-zstandard/blob/main/docs/news.rst">zstandard's changelog</a>.</em></p> <blockquote> <h1>0.25.0 (released 2025-09-14)</h1> <ul> <li>PyO3 Rust created upgraded from 0.24 to 0.25. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/273">#273</a>)</li> <li>We now use <code>Py_REFCNT(obj)</code> instead of accessing <code>(*obj)->ob_refcnt</code> directly. This fixes a nogil / multi-threaded compile error. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/201">#201</a>, <a href="https://redirect.github.com/indygreg/python-zstandard/issues/275">#275</a>)</li> <li>A zstandard commit to fix qsort detection on BSD operating systems has been backported. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/272">#272</a>)</li> <li>The <code>PYTHON_ZSTANDARD_IMPORT_POLICY</code> environment variable now has leading and trailing whitespace stripped. Values like <code> cffi</code> and <code>cffi </code> are now equivalent to <code>cffi</code>.</li> <li>The CI jobs for building wheels have been overhauled to always use <code>cibuildwheel</code> and <code>uv</code> (where possible). This change should be backwards compatible. But wheel building for this project has historically been fragile and there may be unwanted changes. We're optimistic that standardizing on uv (except for musllinux ppc64le and s390x where uv isn't available) will lead to more stability over time.</li> <li>CI now runs tests against the wheels we distribute. Previously, we ran tests against a separate build that was theoretically identical. But the builds may have been subtly different, leading to preventable bugs in our wheels. (Enabling this test coverage did not uncover any failures.)</li> <li>The <code>pyproject.toml</code> build backend has been switched from <code>setuptools.build_meta:__legacy__</code> to <code>setuptools.build_meta</code>.</li> <li>The setuptools build dependency has been upgraded from <69.0.0 to >=77.0.0. Modern versions of setuptools broke <code>--config-settings=--build-option=...</code> as part of implementing PEP 660. A workaround is to use <code>--config-settings=--global-option=...`` instead. </code>--global-option<code>apparently is deprecated and the setuptools folks have yet to figure out how to thread config settings into</code>setup.py<code> invocations. (`--build-option</code> is sent to the <code>build_wheel</code> command but not the <code>build_editable</code> command.)</li> <li>Python 3.14 wheels are now built with <code>manylinux_2_28</code> (versus <code>manylinux2014</code>) for older Python versions. This may raise the minimum glibc version, effectively dropping support for Debian 8 and 9, Ubuntu 13.10 through 18.04, Fedora 19 to 28, and RHEL/Centos 7. However, in practice most platforms don't container newer glibc symbols and are still ABI compatible with <code>manylinux2014</code> and glibc 2.17.</li> <li>We now require cffi >= 2.0.0b on Python 3.14. <3.14 still requires 1.17. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/274">#274</a>)</li> <li>The cffi backend is now automatically disabled for free-threaded builds on Python <3.14, as cffi didn't implement free-threaded support until the 2.0 release. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/274">#274</a>)</li> <li>Added CI coverage for free-threaded CPython 3.13 and 3.14. We do not yet formally support free-threaded builds. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/276">#276</a>)</li> <li>The C and Rust backends now declare the GIL as unused.</li> <li>The <code>pythoncapi_compat.h</code> file has been upgraded to the latest version. (<a href="https://redirect.github.com/indygreg/python-zstandard/issues/278">#278</a>)</li> <li><code>setup.py</code> now depends on <code>packaging</code> and uses <code>packaging.version.Version</code> for version comparisons. This removes some deprecation warnings from usage of legacy distutils <code>Version</code> classes.</li> <li>Relax run-time libzstd version checking in C extension from exactly 1.5.7</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/indygreg/python-zstandard/commit/7a77a7510b8ce068e4a103d29aea1b5ec829d8b6"><code>7a77a75</code></a> global: release 0.25.0</li> <li><a href="https://github.com/indygreg/python-zstandard/commit/79355394165dc87422f6b8a5fcde66069e5eafca"><code>7935539</code></a> rust: <code>cargo upgrade</code></li> <li><a href="https://github.com/indygreg/python-zstandard/commit/bc3074cb2f30d9eb9435ee1042576d31d4f7099e"><code>bc3074c</code></a> rust: update dependencies</li> <li><a href="https://github.com/indygreg/python-zstandard/commit/51a277a795dbca0b9dfce6b45766089b35aef506"><code>51a277a</code></a> c-ext: correctly define fully qualified type names to <code>zstandard.*</code></li> <li><a href="https://github.com/indygreg/python-zstandard/commit/9ccbc39ef2fe86080c5fe9380cde01dbc4627809"><code>9ccbc39</code></a> docs: fix ReST in <code>news.rst</code></li> <li><a href="https://github.com/indygreg/python-zstandard/commit/58c68a185075d5e6a132f5d12b7938279ec60d78"><code>58c68a1</code></a> zstd: synchronize qsort code with upstream</li> <li><a href="https://github.com/indygreg/python-zstandard/commit/395f6932e9c58520a2bb08563163bd2c40b9b103"><code>395f693</code></a> docs: document existence of <code>compression.zstd</code> in stdlib</li> <li><a href="https://github.com/indygreg/python-zstandard/commit/6967817f31c102559ce5e5f474d42f25db451493"><code>6967817</code></a> docs: update comparisons to other implementations</li> <li><a href="https://github.com/indygreg/python-zstandard/commit/e4e829a5362620b5fb3ca594b2ccf844686630bf"><code>e4e829a</code></a> docs: document new libzstd version constraint behaviors</li> <li><a href="https://github.com/indygreg/python-zstandard/commit/604a65a51b96ebae88e0114d32858dd9ac504215"><code>604a65a</code></a> Relax libzstd version checking</li> <li>Additional commits viewable in <a href="https://github.com/indygreg/python-zstandard/compare/0.24.0...0.25.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>
Bumps [pydantic](https://github.com/pydantic/pydantic) from 2.11.7 to 2.11.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pydantic/pydantic/releases">pydantic's releases</a>.</em></p> <blockquote> <h2>v2.11.9 2025-09-13</h2> <h3>What's Changed</h3> <h4>Fixes</h4> <ul> <li>Backport v1.10.23 changes by <a href="https://github.com/Viicos"><code>@Viicos</code></a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/pydantic/pydantic/compare/v2.11.8...v2.11.9">https://github.com/pydantic/pydantic/compare/v2.11.8...v2.11.9</a></p> <h2>v2.11.8 2025-09-13</h2> <h2>v2.11.8 (2025-09-13)</h2> <h3>What's Changed</h3> <h4>Fixes</h4> <ul> <li>Fix mypy plugin for mypy 1.18 by <a href="https://github.com/cdce8p"><code>@cdce8p</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/12209">#12209</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/pydantic/pydantic/compare/v2.11.7...v2.11.8">https://github.com/pydantic/pydantic/compare/v2.11.7...v2.11.8</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pydantic/pydantic/blob/v2.11.9/HISTORY.md">pydantic's changelog</a>.</em></p> <blockquote> <h2>v2.11.9 (2025-09-13)</h2> <p><a href="https://github.com/pydantic/pydantic/releases/tag/v2.11.9">GitHub release</a></p> <h3>What's Changed</h3> <h4>Fixes</h4> <ul> <li>Backport v1.10.23 changes by <a href="https://github.com/Viicos"><code>@Viicos</code></a></li> </ul> <h2>v2.11.8 (2025-09-13)</h2> <p><a href="https://github.com/pydantic/pydantic/releases/tag/v2.11.8">GitHub release</a></p> <h3>What's Changed</h3> <h4>Fixes</h4> <ul> <li>Fix mypy plugin for mypy 1.18 by <a href="https://github.com/cdce8p"><code>@cdce8p</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/12209">#12209</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pydantic/pydantic/commit/92310953c146a2ac668a0141be820c083e325f5d"><code>9231095</code></a> Prepare release v2.11.9</li> <li><a href="https://github.com/pydantic/pydantic/commit/f003a89eeaff35ee18f220a2c790d20536e3d0ab"><code>f003a89</code></a> Backport v1.10.23 changes</li> <li><a href="https://github.com/pydantic/pydantic/commit/96b81ddaf93a1f2e19ff1609080c33de10b8d931"><code>96b81dd</code></a> Prepare release v2.11.8</li> <li><a href="https://github.com/pydantic/pydantic/commit/966f377692194b3f1d6d5155ac78052bec0a751d"><code>966f377</code></a> Fix mypy v2 plugin for upcoming <code>1.18</code> mypy release</li> <li>See full diff in <a href="https://github.com/pydantic/pydantic/compare/v2.11.7...v2.11.9">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>
Bumps [pycparser](https://github.com/eliben/pycparser) from 2.22 to 2.23. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eliben/pycparser/releases">pycparser's releases</a>.</em></p> <blockquote> <h2>release_v2.23</h2> <h2>What's Changed</h2> <ul> <li>Allow abstract declarator "static" (GH issue <a href="https://redirect.github.com/eliben/pycparser/issues/539">#539</a>) by <a href="https://github.com/gperciva"><code>@gperciva</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/545">eliben/pycparser#545</a></li> <li>Add support for Python 3.13 by <a href="https://github.com/hugovk"><code>@hugovk</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/550">eliben/pycparser#550</a></li> <li>Add dirent and socket typedefs. by <a href="https://github.com/MegaManSec"><code>@MegaManSec</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/558">eliben/pycparser#558</a></li> <li>Support for labels with no statement by <a href="https://github.com/ignatirabo"><code>@ignatirabo</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/562">eliben/pycparser#562</a></li> <li>Accept empty 'case' or 'default' labels by <a href="https://github.com/ignatirabo"><code>@ignatirabo</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/564">eliben/pycparser#564</a></li> <li>fix: preserve parentheses for statement exprs by <a href="https://github.com/zawan-ila"><code>@zawan-ila</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/566">eliben/pycparser#566</a></li> <li>fix: hex float types by <a href="https://github.com/zawan-ila"><code>@zawan-ila</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/567">eliben/pycparser#567</a></li> <li>Explicit error for comments, with README link by <a href="https://github.com/cellularmitosis"><code>@cellularmitosis</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/569">eliben/pycparser#569</a></li> <li>showemptyattrs option on Node.show() by <a href="https://github.com/cellularmitosis"><code>@cellularmitosis</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/570">eliben/pycparser#570</a></li> <li>Add fake typedefs for GNU Extension 128-bit integers. by <a href="https://github.com/dj-wednesday"><code>@dj-wednesday</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/577">eliben/pycparser#577</a></li> <li>Typedef for __kernel_sa_family_t in linux/socket.h by <a href="https://github.com/crosser"><code>@crosser</code></a> in <a href="https://redirect.github.com/eliben/pycparser/pull/578">eliben/pycparser#578</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/gperciva"><code>@gperciva</code></a> made their first contribution in <a href="https://redirect.github.com/eliben/pycparser/pull/545">eliben/pycparser#545</a></li> <li><a href="https://github.com/MegaManSec"><code>@MegaManSec</code></a> made their first contribution in <a href="https://redirect.github.com/eliben/pycparser/pull/558">eliben/pycparser#558</a></li> <li><a href="https://github.com/ignatirabo"><code>@ignatirabo</code></a> made their first contribution in <a href="https://redirect.github.com/eliben/pycparser/pull/562">eliben/pycparser#562</a></li> <li><a href="https://github.com/zawan-ila"><code>@zawan-ila</code></a> made their first contribution in <a href="https://redirect.github.com/eliben/pycparser/pull/566">eliben/pycparser#566</a></li> <li><a href="https://github.com/cellularmitosis"><code>@cellularmitosis</code></a> made their first contribution in <a href="https://redirect.github.com/eliben/pycparser/pull/569">eliben/pycparser#569</a></li> <li><a href="https://github.com/dj-wednesday"><code>@dj-wednesday</code></a> made their first contribution in <a href="https://redirect.github.com/eliben/pycparser/pull/577">eliben/pycparser#577</a></li> <li><a href="https://github.com/crosser"><code>@crosser</code></a> made their first contribution in <a href="https://redirect.github.com/eliben/pycparser/pull/578">eliben/pycparser#578</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eliben/pycparser/compare/release_v2.22...release_v2.23">https://github.com/eliben/pycparser/compare/release_v2.22...release_v2.23</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eliben/pycparser/commit/5b60167602e7914139b3e277266ccdff5c24dbf2"><code>5b60167</code></a> Prepare for release 2.23</li> <li><a href="https://github.com/eliben/pycparser/commit/7b24736bbb875a5c6c6f0520412f03aace75d0ee"><code>7b24736</code></a> Typedef for __kernel_sa_family_t in _fake_typedefs.h (<a href="https://redirect.github.com/eliben/pycparser/issues/578">#578</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/90184f1f4eb1234fb9e7ae0c8b74eab9ea963482"><code>90184f1</code></a> Add fake typedefs for GNU Extension 128-bit integers. (<a href="https://redirect.github.com/eliben/pycparser/issues/577">#577</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/f04fdcde3d95be4a632948718d0c46eac09c50ce"><code>f04fdcd</code></a> showemptyattrs option on Node.show() (<a href="https://redirect.github.com/eliben/pycparser/issues/570">#570</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/156eae7f42843d8a3e78a68995d9cc7485577e38"><code>156eae7</code></a> Explicit error for comments, with README link (<a href="https://redirect.github.com/eliben/pycparser/issues/569">#569</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/2215299261306df71e2cec23bb3acd7b8f31f8db"><code>2215299</code></a> fix: hex float types (<a href="https://redirect.github.com/eliben/pycparser/issues/567">#567</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/037bd31d4e0e69e8c4d80e45311ae46abc15dd4e"><code>037bd31</code></a> fix: preserve parentheses for statement exprs (<a href="https://redirect.github.com/eliben/pycparser/issues/566">#566</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/9cecc090151b31d8821786bca3b25851a4a33272"><code>9cecc09</code></a> Accept empty 'case' or 'default' labels (<a href="https://redirect.github.com/eliben/pycparser/issues/564">#564</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/7ae671d3ac44e1000bcbe7108b24bdb9187443ac"><code>7ae671d</code></a> Support for labels with no statement (<a href="https://redirect.github.com/eliben/pycparser/issues/562">#562</a>)</li> <li><a href="https://github.com/eliben/pycparser/commit/42b542324859a108f2cf35bcfe21fe5877ceb091"><code>42b5423</code></a> Add dirent and socket typedefs. (<a href="https://redirect.github.com/eliben/pycparser/issues/558">#558</a>)</li> <li>Additional commits viewable in <a href="https://github.com/eliben/pycparser/compare/release_v2.22...release_v2.23">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>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )