release: bump version to 2.1.0

[finswimmer]

TODO

• set release date in Changelog
• @radoering: add changelog entries for performance improvements
• Add poetry-core Changelog
• Pin poetry-core version

---

Added

• Make build command build-system agnostic (#10059, #10092).
• Add a --config-settings option to poetry build (#10059).
• Add support for defining config-settings when building dependencies (#10129).
• Add (experimental) commands to manage Python installations (#10112).
• Use findpython to find the Python interpreters (#10097).
• Add a --no-truncate option to poetry show (#9580).
• Re-add support for passwords with empty usernames (#10088).
• Add better error messages (#10053, #10065, #10126, #10127, #10132).

Changed

• poetry new defaults to "src" layout by default (#10135).
• Improve performance of locking dependencies (#10111, #10114, #10138, #10146).
• Deprecate adding sources without specifying --priority (#10134).

Fixed

• Fix an issue where global options were not handled correctly when positioned after command options (#10021, #10067, #10128).
• Fix an issue where building a dependency from source failed because of a conflict between build-system dependencies that were not required for the target environment (#10048).
• Fix an issue where poetry init was not able to find a package on PyPI while adding dependencies interactively (#10055).
• Fix an issue where the @latest descriptor was incorrectly passed to the core requirement parser (#10069).
• Fix an issue where Boolean environment variables set to True (in contrast to true) were interpreted as false (#10080).
• Fix an issue where poetry env activate reported a misleading error message (#10087).
• Fix an issue where adding an optional dependency with poetry add --optional would not correctly update the lock file (#10076).
• Fix an issue where pip was not installed/updated before other dependencies resulting in a race condition (#10102).
• Fix an issue where Poetry freezes when multiple threads attempt to unlock the keyring simultaneously (#10062).
• Fix an issue where markers with extras were not locked correctly (#10119).
• Fix an issue where self-referential extras were not resolved correctly (#10106).
• Fix an issue where Poetry could not be run from a zipapp (#10074).
• Fix an issue where installation failed with a permission error when using the system environment as a user without write access to system site packages (#9014).
• Fix an issue where a version of a dependency that is not compatible with the project's python constraint was locked. (#10141).
• Fix an issue where Poetry wrongly reported that the current project's supported Python range is not compatible with some of the required packages Python requirement (#10157).
• Fix an issue where the requested extras of a dependency were ignored if the same dependency (with same extras) was specified in multiple groups (#10158).

Docs

• Sort commands by name in the CLI reference (#10035).
• Add missing documentation for env commands (#10027).
• Clarify that the name and version fields are always required if the project section is specified (#10033).
• Add a note about restarting the shell for tab completion changes to take effect (#10070).
• Fix the example for project.gui-scripts #10121.
• Explain how to include files as scripts in the project configuration (#9572, #10133).
• Add additional information on specifying required python versions (#10104).

poetry-core (2.1.0)

• 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 included in sdists and wheels (#835).

Summary by Sourcery

Prepare for the 2.1.0 release.

New Features:

• Make the build command build-system agnostic.
• Use findpython to find Python interpreters.
• Improve error presentation to users

Tests:

• Fix an incompatibility issue with importlib-resources in a solver test.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the version of Poetry from 2.0.1 to 2.1.0. It also updates the changelog to reflect the changes made in this release.

Sequence diagram for improved dependency resolution

sequenceDiagram
    participant U as User
    participant P as Poetry
    participant S as Dependency Solver
    participant L as Lock File

    U->>P: poetry add --optional dependency
    P->>S: Resolve dependencies
    S->>S: Process constraints with extras
    S->>S: Handle nested extras
    S->>L: Update lock file
    P->>U: Confirm dependency added

Loading

Sequence diagram for improved installation process

sequenceDiagram
    participant U as User
    participant P as Poetry
    participant Pip as Pip
    participant Sys as System

    U->>P: Install dependencies
    P->>P: Check permissions
    P->>Pip: Execute pip operations first
    Pip-->>P: Pip operations complete
    P->>P: Process remaining operations
    P->>Sys: Install wheels
    P-->>U: Installation complete

Loading

Flow diagram of Poetry 2.1.0 major changes

flowchart TD
    subgraph Major_Changes[Major Changes in Poetry 2.1.0]
        A[Build System Agnostic]
        B[Python Interpreter Finding]
        C[Error Presentation]
        D[Default src Layout]
    end

    subgraph Details
        A -->|Uses| A1[Multiple Build Systems]
        B -->|Uses| B1[findpython Package]
        C -->|Improves| C1[User Error Messages]
        D -->|Changes| D1[Default Project Structure]
    end

Loading

File-Level Changes

Change	Details	Files
Bumped the version of Poetry to 2.1.0.	Updated the version field to 2.1.0.	pyproject.toml
Updated the changelog for the 2.1.0 release.	Added a new section for version 2.1.0. Included lists of added, changed, fixed, and documented items. Added links to the relevant pull requests for each change.	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.