Change8

Poetry

Dev Tools

Python packaging and dependency management made easy

Latest: 2.3.211 releases4 breaking changes29 common errorsView on GitHub

Release History

2.3.21 fix
Feb 1, 2026

This release updates the dependency constraint for dulwich to 1.0+ and includes a bug fix in poetry-core related to Windows platform release parsing.

2.3.11 fix
Jan 20, 2026

This release primarily fixes an issue related to package cache invalidation and includes documentation updates for the SHELL_VERBOSITY environment variable.

2.3.0Breaking13 fixes12 features
Jan 18, 2026

This release drops support for Python 3.9, changes the default for installer re-resolution, and introduces significant improvements for PEP 735 dependency groups and artifact publishing.

2.2.12 fixes
Sep 21, 2025

This release fixes a CLI output error in 'poetry self show' and resolves an issue regarding optional PEP 735 dependency groups via a poetry-core update.

2.2.0Breaking4 fixes5 features
Sep 14, 2025

This release introduces support for PEP 735 dependency groups and PEP 639 license clarity, adds JSON output to 'poetry show', and officially supports Python 3.14.

2.1.42 fixes1 feature
Aug 5, 2025

This release pins virtualenv to versions below 20.33, improves pyproject.toml validation messages, and fixes plugin installation and self-referential extras resolution issues.

2.1.3Breaking10 fixes
May 4, 2025

This release pins importlib-metadata<8.7 for Python 3.9 due to upstream breaking changes and includes numerous bug fixes across Poetry and poetry-core.

2.1.210 fixes2 features
Mar 29, 2025

This release focuses on performance improvements for dependency locking and marker operations, alongside several bug fixes for environment activation commands and marker logic determinism.

2.1.12 fixes
Feb 16, 2025

This release fixes two issues: Poetry now correctly selects the Python interpreter when using `poetry env use python`, and Poetry Core no longer produces invalid markers when simplifying `python_version` markers.

2.1.0Breaking19 fixes8 features
Feb 15, 2025

This release introduces experimental Python installation management, makes the build system agnostic, and changes the default project layout to 'src'. It also includes significant performance improvements for dependency locking and numerous bug fixes related to PEP compliance and environment handling.

2.0.19 fixes4 features
Jan 12, 2025

This release introduces support for searching legacy sources and improves dependency resolution performance. It also fixes several critical bugs related to package synchronization, environment detection, and plugin API compatibility.

Common Errors

BrokenPipeError42 reports

BrokenPipeError in Poetry often arises from prematurely terminated processes during installation or dependency resolution, typically due to I/O issues or subprocess failures. To resolve it, ensure sufficient system resources (memory, disk space), update Poetry to the latest version, and clean the Poetry cache (`poetry cache:clear --all`) to eliminate corrupted package data. Retry the operation after these steps.

PoetryRuntimeError28 reports

PoetryRuntimeError often arises from inconsistencies between the poetry.lock file, pyproject.toml file and the actual installed environment, or unmet system dependencies during dependency resolution. Try deleting poetry.lock and the virtual environment directory (usually .venv), then run `poetry install` to rebuild the environment from scratch, ensuring all system dependencies are installed beforehand.

SolverProblemError11 reports

SolverProblemError in Poetry usually arises from conflicting dependencies or constraints within your pyproject.toml file, often due to incompatible version requirements or missing markers for conditional dependencies. Resolve it by carefully reviewing your dependencies, relaxing version constraints (using broader ranges like "~" or "^"), and adding appropriate markers to ensure compatibility based on Python version or environment.

OverrideNeededError10 reports

The "OverrideNeededError" in Poetry usually arises from dependency conflicts during resolution, particularly when a dependency specifies incompatible version constraints or markers for different Python versions. To resolve this, carefully review your pyproject.toml for version constraints and environment markers in dependencies, ensuring they're compatible across your project's supported Python versions. If necessary, use conditional dependencies or environment markers to specify different versions based on the Python environment, like `python = ">=3.10,<3.12"` to address issues such as Python 3.12 compatibility.

EnvCommandError8 reports

EnvCommandError in Poetry usually arises from issues with the Python environment Poetry is trying to use, such as a missing interpreter, incorrect permissions, or conflicts with other Python installations. To resolve this, ensure a valid Python version is installed and accessible, and explicitly configure Poetry to use the correct environment with `poetry env use /path/to/python` or by specifying the `python` configuration option in your `poetry.toml` file. If using virtual environments, activate the intended environment before running Poetry commands.

SolveFailureError8 reports

SolveFailureError in Poetry typically arises from dependency conflicts or unmet version constraints defined in `pyproject.toml`. To resolve this, carefully review your `pyproject.toml` file, paying close attention to version ranges and optional dependencies. Resolve conflicting dependencies by relaxing constraints or, when necessary, explicitly overriding versions to ensure compatibility.

Related Dev Tools Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed