●Change8

Migrating to Poetry 2.4.0

Version 2.4.0 introduces 1 breaking change. This guide details how to update your code.

Released: 5/3/2026

1
Breaking Changes
3
Migration Steps
6
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

`poetry update``poetry debug resolve``poetry env activate``poetry publish``requires-plugins``lazy-wheel`

Breaking Changes

●Issue #1

Running `poetry update <package>` now raises an error if the specified package name is not listed in the project's dependencies, instead of silently ignoring it. Users must ensure the package is defined in `pyproject.toml` to update it via this command.

Migration Steps

  1. 1
    If you were relying on `poetry update <package>` to update a package not listed in your dependencies, you must now add that package to your `[tool.poetry.dependencies]` section first.
  2. 2
    Ensure your `installer` dependency is at least version `1.0.0`.
  3. 3
    Ensure your `findpython` dependency is at least version `0.8`.

Release Summary

This release introduces new solver configuration options to control dependency resolution based on package release age and fixes numerous bugs related to publishing, environment activation, and dependency resolution stability.

Need More Details?

View the full release notes and all changes for Poetry 2.4.0.

View Full Changelog