python-poetry / python-poetry/poetry
Have the `poetry show --outdated` result reflected in its exit code for automation/CI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Feature Request
Poetry has an excellent way of showing packages which are outdated, but are either required to be outdated (as dependencies), or just plain outdated.
For example, here we have poetry installed, which depends on requests, which in turn depends on an outdated idna. We also have an outdated version of docker installed:

I'd like to be able to distinguish in a CI job if there are any packages outdated that can be updated, by result of a non zero exit code from running poetry show --outdated. This should then have a zero exit code when dependencies need to stay outdated.
This would be very useful in keeping things up to date, without having to do any manual work, and having a CI job keep watch on that for me.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the poetry show --outdated command and its current exit-code handling, then inspect the related CLI tests. The change is complete when the command returns a nonzero exit code for outdated packages that can be updated, but zero when packages are outdated only because of dependency constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100