poetry check: distinguish warnings from errors?

[seub]

Issue Kind

Brand new capability

Description

poetry check exits with error code 1 even when there are only warnings and no hard errors.

This is standard UNIX behavior, but it makes it impossible to distinguish warnings from hard errors.

Example scenario

When upgrading Poetry to 2.0, my project.toml file caused poetry check to raise warnings, and exit with exit code 1:

I don't have a problem with that, but it seems inconvenient that there is no way to check for warnings vs hard errors.

Suggested solutions

Here are two ideas:

1. Exit with error code 2 when there are only warnings and no hard errors
2. Add a flag --soft-warnings causing poetry check to pass (exit code 0) when there are only warnings and no hard errors

Workarounds

Suboptimal workaroung:

poetry check || echo "Some errors or warnings were raised by 'poetry check'"

[gridhead]

As mentioned before here #9965 (comment),

I'm going to chime in having the same observations as @Zlopez here with a couple of my projects.

If those are warnings - a non-zero exit code coming as a result of an impending release breaks things.

Context. https://github.com/fedora-infra/mdapi/actions/runs/12646184815/job/35236500953

Context. https://github.com/fedora-infra/firmitas/actions/runs/12624139412/job/35173984552#step:5:21

[futurwasfree]

+1 here this one stops us from migration to 2.0

[przemyslaw-sitek]

poetry check exits with error code 1 even when there are only warnings and no hard errors.

This is standard UNIX behavior, but it makes it impossible to distinguish warnings from hard errors.

I disagree. Most tools report success exit code if no errors were encountered, and tools that do, that feature requires explicit opt-in. For example gcc returns 0 exit code unless -Werror (Make all warnings into errors) option was explicitly provided.