Bump setuptools from 65.6.3 to 77.0.1

[dependabot]

Bumps setuptools from 65.6.3 to 77.0.1.

Changelog

Sourced from setuptools's changelog.

v77.1.1

Bugfixes

• Manually fix news fragment entries causing CI to crash when building docs. (#4891)

v77.0.0

Features

• Added initial support for license expression (PEP :pep:639 <639#add-license-expression-field>). -- by :user:cdce8p (#4706)
• Store License-File\s in .dist-info/licenses subfolder and added support for recursive globs for license_files (PEP :pep:639 <639#add-license-expression-field>). -- by :user:cdce8p (#4728)
• Bump core metadata version to 2.4. -- by :user:cdce8p (#4830)
• Updated vendored copy of wheel to v0.45.1. (#4869)

Deprecations and Removals

• Added initial implementation of :pep:639. Users relying on pre- :pep:639 implementation details (like precise license file paths inside dist-info directory) may need to adjust their code base to avoid problems. Deprecations and stronger validation were also introduced (#4829).
• Added exception (or warning) when deprecated license classifiers are used, according to PEP :pep:639 <639#deprecate-license-classifiers>. (#4833)
• Deprecated tools.setuptools.license-files in favor of project.license-files and added exception if project.license-files and tools.setuptools.license-files are used together. -- by :user:cdce8p (#4837)
• Deprecated project.license as a TOML table in pyproject.toml. Users are expected to move towards using project.license-files and/or SPDX expressions (as strings) in pyproject.license. See PEP :pep:639 <639#deprecate-license-key-table-subkeys>. (#4840)
• Added simple validation for given glob patterns in license-files: a warning will be generated if no file is matched. Invalid glob patterns can raise an exception. -- thanks :user:cdce8p for contributions. (#4838)

Misc

• #4734

... (truncated)

Commits

• f577461 Bump version: 77.0.0 → 77.0.1
• 85677af Manually fix news fragment entries (#4891)
• ce2e283 Change news fragment name to imply patch version bump
• 7653149 Add news fragments
• 7db26a1 Manually fix news fragment entries
• 5d58b45 Bump version: 76.1.0 → 77.0.0
• f49d589 Update URL in warning
• dee0a5e Add news fragment for PEP 639 marking as 'breaking'
• 74725de Update vendored copy of wheel (#4869)
• 5585c1c Add news fragment
• 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 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)

Summary by Sourcery

Chores:

• Update setuptools dependency from 65.6.3 to 77.0.1.

[dependabot]

Labels

The following labels could not be found: pip dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the setuptools dependency from version 65.6.3 to 77.0.1. The update includes new features related to PEP 639 (license expressions), deprecations of older license configurations, and an updated vendored version of wheel.

Updated class diagram for setuptools license handling (PEP 639)

classDiagram
    class PackageMetadata {
        -license: str
        -license_files: list
        +add_license(license: str)
        +add_license_file(file: str)
    }
    note for PackageMetadata "Supports SPDX license expressions and license files"

    class ProjectConfig {
        -license: str [deprecated]
        -license_files: list
    }
    note for ProjectConfig "project.license as TOML table is deprecated. Use SPDX expressions or project.license-files instead."

Loading

File-Level Changes

Change	Details	Files
The pull request updates the setuptools dependency from version 65.6.3 to 77.0.1.	Updated setuptools to the latest version.	requirements.txt
The new version of setuptools includes initial support for license expression (PEP 639), stores License-Files in .dist-info/licenses subfolder, bumps core metadata version to 2.4, and updates the vendored copy of wheel to v0.45.1.	Added initial support for license expression (PEP 639). Stored License-Files in .dist-info/licenses subfolder and added support for recursive globs for license_files (PEP 639). Bumped core metadata version to 2.4. Updated vendored copy of wheel to v0.45.1.
The new version of setuptools includes deprecations and removals related to PEP 639, including deprecating tools.setuptools.license-files and project.license as a TOML table.	Added initial implementation of PEP 639 with potential adjustments needed for users relying on pre-PEP 639 implementation details. Added exception (or warning) when deprecated license classifiers are used, according to PEP 639. Deprecated tools.setuptools.license-files in favor of project.license-files and added exception if both are used together. Deprecated project.license as a TOML table, recommending the use of project.license-files and/or SPDX expressions. Added simple validation for glob patterns in license-files, generating a warning if no file is matched.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[dependabot]

Superseded by #261.