Repository navigation
deps: re-allow installer 0.7.0 - #10887
Conversation
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
Documentation Updates 1 document(s) were updated by changes in this PR: CHANGELOGView Changes@@ -12,7 +12,7 @@
- Raise an error instead of silently ignoring a package name that is not a dependency when it is passed to `poetry update` ([#10721](https://github.com/python-poetry/poetry/pull/10721)).
- Automatically add a trailing slash to legacy repository URLs (used for publishing) if missing ([#10785](https://github.com/python-poetry/poetry/pull/10785)).
-- Require `installer>=1.0.0` ([#10869](https://github.com/python-poetry/poetry/pull/10869)).
+- Require `installer>=0.7.0`. Although the minimum required installer version was bumped to `1.0.0` to fix [#10028](https://github.com/python-poetry/poetry/issues/10028) ([#10869](https://github.com/python-poetry/poetry/pull/10869)), it was reverted to `0.7.0` due to issues with system package managers ([#10882](https://github.com/python-poetry/poetry/issues/10882), [#10887](https://github.com/python-poetry/poetry/pull/10887)).
- Allow `findpython>=0.8` ([#10874](https://github.com/python-poetry/poetry/pull/10874)).
### FixedHow did I do? Any feedback? |
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [poetry](https://github.com/python-poetry/poetry) ([changelog](https://python-poetry.org/history/)) | patch | `2.4.0` → `2.4.1` | --- ### Release Notes <details> <summary>python-poetry/poetry (poetry)</summary> ### [`v2.4.1`](https://github.com/python-poetry/poetry/blob/HEAD/CHANGELOG.md#241---2026-05-09) [Compare Source](python-poetry/poetry@2.4.0...2.4.1) ##### Changed - Re-allow `installer==0.7.0` ([#​10887](python-poetry/poetry#10887)). ##### Fixed - Fix an issue where `poetry update <package>` failed when `<package>` was a transitive dependency ([#​10885](python-poetry/poetry#10885)). </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNzAuMTkiLCJ1cGRhdGVkSW5WZXIiOiI0My4xNzAuMTkiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=--> Reviewed-on: https://git.walbeck.it/mwalbeck/docker-python-poetry/pulls/1744
|
Now that pypa/installer#325 (that caused #10882) is fixed in installer v1.0.1, may you consider bumping the minimum required |
Can you elaborate? Poetry 2.4.1 allows installer 1.0.1 and most of the ways to install Poetry should pick the latest installer by default. And even if they do not there is probably a way to force installer 1.0.1. In other words, I cannot imagine that a downgrade should be the only possible fix. |
Ok you're right, turns out pipx doesn't upgrade dependencies if it doesn't need to? So it reused installer 0.7.0. I had to fully uninstall Poetry then reinstall it and now it uses 1.0.1. Phew |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Pull Request Check List
Resolves: #10882
In #10869, we bumped the minimum required installer version because it fixes #10028.
However, there is another issue in the new installer version. See #10882 for details. Although the issue may not be relevant for Poetry itself, it is an issue for system package managers.
Re-allowing the older installer version should not hurt because it still works with Poetry (except for the specific use case described in #10028) and most users will get the latest version anyway.