[dependabot]

Bumps setuptools from 84.0.0 to 84.1.0.

Changelog

Sourced from setuptools's changelog.

v84.1.0

Features

• setuptools.archive_util now raises the new UnsafeMember 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 tarfile extraction filters.

Bugfixes

• Wheel.install_as_egg no longer creates namespace package directories outside of the destination egg directory. Entries in a wheel's namespace_packages.txt were split on . and passed straight to os.path.join, so an entry that was absolute, drive-qualified, or UNC discarded the destination and placed an __init__.py at a path chosen by the wheel. Namespace entries are now validated as dotted module names on every platform -- see GHSA-xmj3-9gf7-h52w.

  This code path is reached only by the deprecated setup_requires mechanism when setup() is invoked outside a PEP 517 frontend; the setuptools build backend never reaches it.

• setuptools.archive_util no longer extracts archive members outside of the requested extraction directory. Both the tar and zip formats specify / as the only path separator, but the guard against .. components split member names on / alone, so a name such as ..\escaped.txt 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.

Commits

• 77b7ace Bump version: 84.0.0 → 84.1.0
• e66004c Merge pull request #5329 from pypa/fix/wheel-namespace-path-escape
• 54b5dca Cover the containment check with a symlink escape test
• 6d07b8d Validate namespace package names during legacy wheel installation
• 8419f00 Merge pull request #5356 from pypa/skeleton-ruff-0.16
• 6dadc86 Remove DTZ011 suppressions that Ruff 0.17 reports as unused.
• 715ec38 Merge https://github.com/jaraco/skeleton
• 9695460jaraco/skeleton#219
• 9e08129jaraco/skeleton#216
• 4e612f9 Ignore PyPy's deprecated check_home warning in tests
• 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 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.

---

Note

Low Risk
Dev-only lockfile update for setuptools with no runtime or application code changes; minor risk if local installs depend on old lock marker behavior.

Overview
Regenerates poetry.lock to bump the dev dependency setuptools from 84.0.0 to 84.1.0 (security and archive-extraction fixes in upstream setuptools). The lockfile header reflects Poetry 2.5.1 (was 2.4.1).

Alongside the version bump, the diff includes lockfile housekeeping from re-resolution: simplified NVIDIA/CUDA package markers, removal of a duplicate nvidia-cusparse entry, minor reordering of optional-extra markers (sweep / migrate), and normalized dependency spec strings for wandb (e.g. gitpython, protobuf) and torchvision’s Pillow constraint. No application source or pyproject.toml changes.

^{Reviewed by Cursor Bugbot for commit ec4c691. Configure here.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: cb079ef1-35e0-4179-aa7b-997cd601f62d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[strix-security]

Strix is installed on this repository, but we couldn't run this PR security review because this workspace's trial has ended. Add a card to resume code reviews here.

So far, Strix has reviewed 42 pull requests and surfaced 2 security issues across this workspace.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit ec4c691. Configure here.}

[cursor]

Overlapping NVIDIA package install markers

High Severity

Regenerating the lock with Poetry 2.5.1 dropped the platform exclusions on fallback nvidia-cublas 13.6.1.10 and nvidia-cuda-nvrtc 13.3.33, so their markers now match the same Linux environments as the torch-pinned 13.1.1.3 and 13.0.88 entries. poetry install can therefore pick or overwrite with the wrong CUDA libraries on Linux, including CI which still uses Poetry 2.1.1.

Additional Locations (1)

• poetry.lock#L2031-L2032

 

^{Reviewed by Cursor Bugbot for commit ec4c691. Configure here.}