dependabot[bot] opened a new pull request, #40763: URL: https://github.com/apache/beam/pull/40763
Bumps [setuptools](https://github.com/pypa/setuptools) from 84.0.0 to 84.1.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pypa/setuptools/blob/main/NEWS.rst";>setuptools's changelog</a>.</em></p> <blockquote> <h1>v84.1.0</h1> <h2>Features</h2> <ul> <li><code>setuptools.archive_util</code> now raises the new <code>UnsafeMember</code> exception when an archive member would be extracted outside of the extraction directory, where previously such a member was silently skipped. Aborting makes a malicious or malformed archive visible to the caller instead of yielding a quietly incomplete extraction, and matches the behavior of the standard library's <code>tarfile</code> extraction filters.</li> </ul> <h2>Bugfixes</h2> <ul> <li> <p><code>Wheel.install_as_egg</code> no longer creates namespace package directories outside of the destination egg directory. Entries in a wheel's <code>namespace_packages.txt</code> were split on <code>.</code> and passed straight to <code>os.path.join</code>, so an entry that was absolute, drive-qualified, or UNC discarded the destination and placed an <code>__init__.py</code> at a path chosen by the wheel. Namespace entries are now validated as dotted module names on every platform -- see GHSA-xmj3-9gf7-h52w.</p> <p>This code path is reached only by the deprecated <code>setup_requires</code> mechanism when <code>setup()</code> is invoked outside a PEP 517 frontend; the setuptools build backend never reaches it.</p> </li> <li> <p><code>setuptools.archive_util</code> no longer extracts archive members outside of the requested extraction directory. Both the tar and zip formats specify <code>/</code> as the only path separator, but the guard against <code>..</code> components split member names on <code>/</code> alone, so a name such as <code>..\escaped.txt</code> was treated as a single component and then resolved as a traversal by the filesystem on Windows. Member names containing a backslash, a drive letter, or a UNC prefix are now rejected on every platform, as are members whose resolved destination falls outside the extraction directory -- see GHSA-grgh-hr87-3jpw.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pypa/setuptools/commit/77b7ace0aaf660beeb9b3f9da4aabf21cbcf3fa9";><code>77b7ace</code></a> Bump version: 84.0.0 → 84.1.0</li> <li><a href="https://github.com/pypa/setuptools/commit/e66004c64eaf6cf2f8c53ccdfac75cf7abce7ccf";><code>e66004c</code></a> Merge pull request <a href="https://redirect.github.com/pypa/setuptools/issues/5329";>#5329</a> from pypa/fix/wheel-namespace-path-escape</li> <li><a href="https://github.com/pypa/setuptools/commit/54b5dcadc1bd938a5a66919e8ab7bcd59805e7fd";><code>54b5dca</code></a> Cover the containment check with a symlink escape test</li> <li><a href="https://github.com/pypa/setuptools/commit/6d07b8d17890dda58d944ac51e58f54af92d52af";><code>6d07b8d</code></a> Validate namespace package names during legacy wheel installation</li> <li><a href="https://github.com/pypa/setuptools/commit/8419f006d4e34c4ecfc7a0bd1bc6993855adc3cc";><code>8419f00</code></a> Merge pull request <a href="https://redirect.github.com/pypa/setuptools/issues/5356";>#5356</a> from pypa/skeleton-ruff-0.16</li> <li><a href="https://github.com/pypa/setuptools/commit/6dadc86a3f7dbe1cf49c6301548ffde61d4e74e1";><code>6dadc86</code></a> Remove DTZ011 suppressions that Ruff 0.17 reports as unused.</li> <li><a href="https://github.com/pypa/setuptools/commit/715ec38b46424533806195a96983e3dd70fdf3b9";><code>715ec38</code></a> Merge <a href="https://github.com/jaraco/skeleton";>https://github.com/jaraco/skeleton</a></li> <li><a href="https://github.com/pypa/setuptools/commit/9695460ebfa879ada16545d62b26b9a489a6d5ed";><code>9695460</code></a><code>jaraco/skeleton#219</code></li> <li><a href="https://github.com/pypa/setuptools/commit/9e0812976b1154a7aece47188814385c887bc6c9";><code>9e08129</code></a><code>jaraco/skeleton#216</code></li> <li><a href="https://github.com/pypa/setuptools/commit/4e612f9e44ecfad130d0b2a27a2dce0740599b4b";><code>4e612f9</code></a> Ignore PyPy's deprecated check_home warning in tests</li> <li>Additional commits viewable in <a href="https://github.com/pypa/setuptools/compare/v84.0.0...v84.1.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 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](https://github.com/apache/beam/network/alerts). </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]
