Bump setuptools from 70.3.0 to 71.0.3 in the general group across 1 directory

[dependabot]

Bumps the general group with 1 update in the / directory: setuptools.

Updates setuptools from 70.3.0 to 71.0.3

Changelog

Sourced from setuptools's changelog.

v71.0.3

Bugfixes

• Reset the backports module when enabling vendored packages. (#4476)

v71.0.2

Bugfixes

• Include all vendored files in the sdist. (#4480)

v71.0.1

Bugfixes

• Restored package data that went missing in 71.0. This change also incidentally causes tests to be installed once again. (#4475)

v71.0.0

Deprecations and Removals

• Now setuptools declares its own dependencies in the core extra. Dependencies are still vendored for bootstrapping purposes, but setuptools will prefer installed dependencies if present. The core extra is used for informational purposes and should not be declared in package metadata (e.g. build-requires). Downstream packagers can de-vendor by simply removing the setuptools/_vendor directory. Since Setuptools now prefers installed dependencies, those installing to an environment with old, incompatible dependencies will not work. In that case, either uninstall the incompatible dependencies or upgrade them to satisfy those declared in core. (#2825)

Commits

• 6d915ca Bump version: 71.0.2 → 71.0.3
• fddda37 Merge pull request #4486 from pypa/bugfix/4476-reset-backports
• 299d276 Reset the backports module when enabling vendored packages.
• 17b735a Bump version: 71.0.1 → 71.0.2
• 5a59af4 Merge pull request #4485 from pypa/bugfix/4480-vendored-metadata
• 65e00b6 Include all vendored files in the sdist.
• 284e8af Add a failing test covering the missed expectation.
• ea5ce1a Update changelog to reflect common experience seen in #4478 and #4483.
• f2a6bb1 Bump version: 71.0.0 → 71.0.1
• 87afa4b Merge pull request #4479 from pypa/bugfix/4475-all-the-files
• 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 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 <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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
pip/setuptools	71.0.3	🟢 6.1	Details Check Score Reason Code-Review 🟢 5 Found 7/13 approved changesets -- score normalized to 5 Maintained 🟢 10 30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy 🟢 10 security policy file detected Packaging ⚠️ -1 packaging workflow not detected Branch-Protection ⚠️ 0 branch protection not enabled on development/release branches Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Vulnerabilities 🟢 10 0 existing vulnerabilities detected Binary-Artifacts ⚠️ 0 binaries present in source code Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Fuzzing 🟢 10 project is fuzzed

Scanned Manifest Files

requirements.txt

• setuptools@71.0.3
• setuptools@70.3.0