Cleo v1.0.0 is not compatible and breaks poetry

[akshitkrnagpal]

• Poetry version: latest
• Python version: any
• OS version and name: any
• pyproject.toml: Not required

• I am on the latest stable Poetry version, installed using a recommended method.
• I have searched the issues of this repo and believe that this is not a duplicate.
• I have consulted the FAQ and blog for any relevant entries or release notes.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue

Cleo's latest release broke latest version of poetry. More specifically this change. python-poetry/cleo#179 released in https://github.com/python-poetry/cleo/releases/tag/1.0.0.

Poetry uses cleo = "^1.0.0a5" which I guess satisfies 1.0.0 but now the error cannot import name 'CleoException' from 'cleo.exceptions' is being thrown.

PS - Sorry if it's a poorly written issue.

[akshitkrnagpal]

1.0.0 is yanked and 2.0.0 will be released. Closing this issue.

[neersighted]

From Discord:

Cleo reached a major milestone today, with the release of the 1.0.0 version, which resolved a number of long-standing bugs, while dropping the dependency on clikit and achieving full type-checking.

Unfortunately, to bring in fixes faster, Poetry had been depending on a pre-release version of Cleo. Breaking changes were made in-between releases related to typing and linting. Due to an oversight in our constraint strategy, we were using a >= range to depend on Cleo alpha versions (instead of pinning, which may have been more advisable). As such, recent versions of Poetry started to pull in Cleo 1.0.0, due to the >=1.0.0a5,<2.0.0 constraint.

Cleo 1.0.0 has been yanked; please restart your CI jobs if you were affected by this broken release. 2.0.0 will be released shortly for consumption in (future versions of) Poetry; the major version bump will prevent this from repeating again.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.