blog: announce Poetry 2.2.0

Author: radoering

content/blog/2025-09-14-announcing-poetry-2-2-0.md

@@ -0,0 +1,145 @@
+---
+layout: single
+title: "Announcing Poetry 2.2.0"
+date: 2025-09-14
+categories: [releases]
+tags: ["2.x", "2.2"]
+---
+
+The Poetry team is pleased to announce the immediate availability of Poetry **2.2.0**.
+
+<!--more-->
+
+If you have a previous version of Poetry installed via `pipx`,
+getting Poetry **2.2.0** is as easy as:
+
+```bash
+$ pipx upgrade poetry
+```
+
+If you used the [official installer](/docs/#installation), you can run:
+
+```bash
+$ poetry self update
+```
+
+## Highlights
+
+### Normalizing dependency group names and nesting dependency groups
+
+By nesting dependency groups, you can include dependencies from one group in another group.
+This is useful when you want to aggregate dependencies from multiple groups into a single group, e.g.:
+
+```toml
+[tool.poetry.group.test.dependencies]
+pytest = "^8.0.0"
+
+[tool.poetry.group.lint.dependencies]
+ruff = "^0.11"
+
+[tool.poetry.group.dev]
+include-groups = [
+    "test",
+    "lint",
+]
+
+[tool.poetry.group.dev.dependencies]
+tox = "*"
+```
+
+In this example, the `dev` group includes all dependencies from the `test` and `lint` groups.
+
+In order to support nesting groups, Poetry will normalize group names.
+This has the side effect that it is no more possible to define two groups with names
+that will result in the same normalized name, e.g. `Test` and `test`.
+
+### Add support for PEP 735 dependency groups
+
+Instead of using Poetry's custom syntax for defining dependency groups, you can now also use
+[PEP 735](https://peps.python.org/pep-0735/) syntax.
+
+For example, instead of
+
+```toml
+[tool.poetry.group.test.dependencies]
+pytest = "^6.0.0"
+pytest-mock = "*"
+```
+
+you can now also write
+
+```toml
+[dependency-groups]
+test = [
+    "pytest (>=6.0.0,<7.0.0)",
+    "pytest-mock",
+]
+```
+
+You can also nest dependency groups via `include-group`:
+
+```toml
+[dependency-groups]
+test = [
+    "pytest (>=8.0.0,<9.0.0)",
+]
+lint = [
+    "ruff (>=0.11.0,<0.12.0)",
+]
+dev = [
+    { include-group = "test" },
+    { include-group = "lint" },
+    "tox",
+]
+```
+
+{{% note %}}
+As with `project.dependencies` and `tool.poetry.dependencies`, you can also
+add additional information about a dependency of a group in the Poetry specific section
+even when using PEP 735 syntax. However, pay attention that you cannot add additional
+dependencies in the Poetry specific section when using PEP 735 syntax;
+you can only add additional information to dependencies.
+{{% /note %}}
+
+### Add support for PEP 639 licencse clarity
+
+With [PEP 639](https://peps.python.org/pep-0639/), table values for the `project.license`
+as well as license classifiers are deprecated.
+`project.license` should be a string representing a valid
+[SPDX expression](https://packaging.python.org/en/latest/glossary/#term-License-Expression).
+License files can be specified in the `project.license-files` table.
+
+Example:
+
+```toml
+[project]
+# ...
+license = "MIT"
+license-files = [
+    "*-LICENSE",
+    "CONTRIBUTORS",
+    "MY-SPECIAL-LICENSE-DIR/**/*"
+]
+```
+
+Further, license files are not anymore put into top-level into the `dist-info` directory
+but into a `licenses` subdirectory.
+
+{{% note %}}
+If you do not specify license files explicitly,
+Poetry will include common license file names by default as before.
+{{% /note %}}
+
+## Upcoming Changes
+
+### Defaulting to `setuptools` instead of `poetry-core` if no build system is defined
+
+Per [PEP 517](https://peps.python.org/pep-0517/), a build tool should fall back to `setuptools` if no build system is
+defined in the `[build-system]` section of `pyproject.toml`. However, to avoid immediate disruption, Poetry will
+currently issue a **warning** in such cases and continue using the built-in `poetry-core` backend by default.
+This behavior will change in a future minor release so that Poetry will default to `setuptools`
+if no `[build-system]` section is defined.
+
+## Changelog
+
+TODO

content/history.md

@@ -4,6 +4,8 @@ layout: single
 title: History
 ---
 
+## TODO: add 2.2.0
+
 ## [2.1.4] - 2025-08-05
 
 ### Changed
@@ -2415,7 +2417,8 @@ This release **must** be downloaded via the `get-poetry.py` script and not via t
 
 Initial release
 
-[Unreleased]: https://github.com/python-poetry/poetry/compare/2.1.4...main
+[Unreleased]: https://github.com/python-poetry/poetry/compare/2.2.0...main
+[2.2.0]: https://github.com/python-poetry/poetry/releases/tag/2.2.0
 [2.1.4]: https://github.com/python-poetry/poetry/releases/tag/2.1.4
 [2.1.3]: https://github.com/python-poetry/poetry/releases/tag/2.1.3
 [2.1.2]: https://github.com/python-poetry/poetry/releases/tag/2.1.2

pyproject.toml

@@ -63,7 +63,7 @@ tags = "/blog/tag/:title/"
 description = "Python dependency management and packaging made easy"
 
 [tool.website.config.params.documentation]
-defaultVersion = "2.1"
+defaultVersion = "2.1"  # TODO: update
 
 [tool.website.config.markup.goldmark.renderer]
 unsafe = true
@@ -72,7 +72,7 @@ unsafe = true
 keepWhitespace = true
 
 [tool.website.versions]
-"2.1" = "2.1"
+"2.1" = "2.1"  # TODO: update
 "1.8" = "1.8"
 
 [build-system]