relase: bump version to 2.3.0

[radoering]

Added

• Add (optional) size and upload_time to Link and Package.files (#905).

Changed

• Drop support for Python 3.9 (#897).
• Normalize versions (#893).
• Remove helper function to create temporary directories (#337).
• Improve type hint of Package.files (#904).
• Update list of supported licenses (#890,
  #895).

Fixed

• Fix an issue where unsatisfiable requirements did not raise an error (#891).
• Fix an issue where the implicit main group did not exist if it was explicitly declared as not having any dependencies (#892).
• Fix an issue where python_full_version markers with pre-release versions were parsed incorrectly (#893).

[sourcery-ai]

Reviewer's Guide

Release prep for version 2.3.0: update package version metadata and changelog, including release links and comparison URLs.

File-Level Changes

Change	Details	Files
Add 2.3.0 release notes to the changelog and update comparison links.	Insert new 2.3.0 section in CHANGELOG with Added/Changed/Fixed subsections mirroring prior merged PRs. Update the Unreleased comparison link to start from 2.3.0 instead of 2.2.1. Add a new 2.3.0 tag link entry alongside prior release links.	CHANGELOG.md
Bump the project version from 2.2.1 to 2.3.0 in code and metadata.	Update the project.version field in pyproject.toml from 2.2.1 to 2.3.0. Update the version constant in the top-level package init to 2.3.0.	pyproject.toml src/poetry/core/__init__.py

---

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!

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]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `CHANGELOG.md:19-21` </location>
<code_context>
+### Fixed
+
+- Fix an issue where unsatisfiable requirements did not raise an error ([#891](https://github.com/python-poetry/poetry-core/pull/891)).
+- Fix an issue where the implicit main group did not exist if it was explicitly declared not having any dependencies ([#892](https://github.com/python-poetry/poetry-core/pull/892)).
+- Fix an issue where `python_full_version` markers with pre-release versions were parsed incorrectly ([#893](https://github.com/python-poetry/poetry-core/pull/893)).
+
</code_context>

<issue_to_address>
**suggestion (typo):** Consider rephrasing "explicitly declared not having any dependencies" for smoother grammar.

For example: “explicitly declared as not having any dependencies” or “explicitly declared to not have any dependencies.”

```suggestion
### Fixed

- Fix an issue where unsatisfiable requirements did not raise an error ([#891](https://github.com/python-poetry/poetry-core/pull/891)).
- Fix an issue where the implicit main group did not exist if it was explicitly declared as not having any dependencies ([#892](https://github.com/python-poetry/poetry-core/pull/892)).
- Fix an issue where `python_full_version` markers with pre-release versions were parsed incorrectly ([#893](https://github.com/python-poetry/poetry-core/pull/893)).
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}