release: bump version to 2.1.0

[finswimmer]

TODO

• set release date in Changelog
• @radoering: add changelog entries for performance improvements
• add changelog entry for PEP 735

---

Added

• Pass a local version label to build backend interface (#814).
• Expose build-system dependencies via the poetry instance (#319).
• Add has_upper_bound method to VersionConstraint (#833).

Changed

• Improve performance of calculating intersections and unions of extra markers (#818).
• Improve performance of calculating intersections and unions of complex markers (#821, #832).
• Improve performance of marker operations by simplifying python_version markers (#826).
• Improve performance by caching parsed requirements (#828).
• Improve error message when a referenced license file is missing (#827).

Fixed

• Fix an issue where inclusive ordering with post releases was inconsistent with PEP 440 (#379).
• Fix an issue where invalid URI tokens in PEP 508 requirement strings were silently discarded (#817).
• Fix an issue where wrong markers were calculated when removing parts covered by the project's python constraint (#824).
• Fix an issue where optional dependencies that are not part of an extra were included in the wheel metadata (#830).
• Fix an issue where the __pycache__ directory and *.pyc files were includes in sdists and wheels (#835).

Summary by Sourcery

Bump version to 2.1.0.

New Features:

• Pass local version label to build backend interface.
• Add support for AtomicMultiMarker and AtomicMarkerUnion for extra markers.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the version of poetry-core to 2.1.0 and includes several additions and fixes. The changes include updates to the changelog, pyproject.toml, and the init file to reflect the new version. Additions include passing local version labels to the build backend interface and adding support for atomic multi-markers. Fixes address issues related to inclusive ordering, invalid URI tokens, performance of marker intersection, missing license files, and optional dependencies in wheel metadata.

Class diagram showing the addition of atomic marker support

classDiagram
    class AtomicMultiMarker {
        +evaluate(environment)
    }
    class AtomicMarkerUnion {
        +evaluate(environment)
    }
    class BaseMarker {
        +evaluate(environment)
    }
    BaseMarker <|-- AtomicMultiMarker
    BaseMarker <|-- AtomicMarkerUnion
    note for AtomicMultiMarker "New marker type for handling
multiple conditions atomically"
    note for AtomicMarkerUnion "New marker type for handling
union of atomic conditions"

Loading

File-Level Changes

Change	Details	Files
Bumped the version of poetry-core to 2.1.0.	Updated the version field in pyproject.toml. Updated the __version__ variable in src/poetry/core/__init__.py.	pyproject.toml src/poetry/core/__init__.py
Updated the changelog to include the release notes for version 2.1.0.	Added a new section for version 2.1.0 with release date. Included 'Added' entries for passing local version label and adding support for atomic multi-markers. Included 'Fixed' entries for inclusive ordering, invalid URI tokens, marker intersection performance, missing license file reporting, and optional dependencies in wheel metadata. Updated the [Unreleased] link to compare against version 2.1.0. Added a link to the release tag for 2.1.0.	CHANGELOG.md

---

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.

[radoering]

I added changelog entries for the performance improvements and all other changes that were merged in the meantime.