blog: announce Poetry 2.1.0

Author: finswimmer

content/blog/2025-02-xx-announcing-poetry-2-1-0.md

@@ -0,0 +1,76 @@
+---
+layout: single
+title: "Announcing Poetry 2.1.0"
+date: 2025-02-xx
+categories: [ releases ]
+tags: [ "2.x", "2.1" ]
+---
+
+The Poetry team is pleased to announce the immediate availability of Poetry **2.1.0**.
+
+<!--more-->
+
+If you have a previous version of Poetry installed via `pipx`,
+getting Poetry **2.1.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
+
+### Support for Alternative Build Backends in Poetry
+
+Poetry now supports customizable build backends, allowing greater flexibility based on your project's needs. Previously,
+Poetry exclusively used its own build backend, `poetry-core`, when creating packages via the `poetry build` command.
+Thanks to [PEP 621](https://peps.python.org/pep-0621/), this limitation is being lifted.
+
+With this change, the `poetry build` command will fully respect the `[build-system]` section defined in your
+`pyproject.toml` file. If the specified build backend differs from the version of `poetry-core` bundled with Poetry, the
+build will take place in an isolated environment.
+
+#### Defining Custom Build Backends
+
+You can define the build backend in your `pyproject.toml`. For example, to use `maturin` as your build system, specify
+it like this:
+
+```toml
+[build-system]
+requires = ["maturin>=0.8.1,<0.9"]
+build-backend = "maturin"
+```
+
+When running `poetry build`, Poetry will create an isolated environment with the specified requirements.
+
+#### Passing Configuration to Build Systems
+
+If your chosen build system supports custom configuration settings, these can be passed via the new `--config-settings`
+parameter. Use the format `--config-settings <key>=<value>`. You can pass multiple settings by using the parameter
+repeatedly.
+
+For example, `poetry-core` allows you to specify a local version identifier during the build:
+
+```bash
+poetry build --config-settings local-version=some-local
+```
+
+This parameter ensures compatibility with advanced use cases and third-party build backends.
+
+#### Default Behavior When 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.
+
+**Note:** This behavior will change in the next minor release of Poetry. When a `[build-system]` section is not defined,
+Poetry will then default to using `setuptools`.
+
+## Changelog
+
+TODO

content/history.md

@@ -4,6 +4,10 @@ layout: single
 title: History
 ---
 
+## [2.1.0] - 2025-02-xx
+
+TODO
+
 ## [2.0.1] - 2025-01-11
 
 ### Added
@@ -2268,7 +2272,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.0.1...main
+[Unreleased]: https://github.com/python-poetry/poetry/compare/2.1.0...main
+[2.1.0]: https://github.com/python-poetry/poetry/releases/tag/2.1.0
 [2.0.1]: https://github.com/python-poetry/poetry/releases/tag/2.0.1
 [2.0.0]: https://github.com/python-poetry/poetry/releases/tag/2.0.0
 [1.8.5]: https://github.com/python-poetry/poetry/releases/tag/1.8.5