Skip to content

Use poetry 2.0.1, lock installed poetry version in Dockerfile #8255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

endothermicdev
Copy link
Collaborator

Checklist

  • The changelog has been updated in the relevant commit(s) according to the guidelines.
  • Tests have been added or modified to reflect the changes.
  • Documentation has been reviewed and updated as needed.
  • Related issues have been listed and linked, including any that this PR closes.

This caused issues in the last release where the installed poetry version was newer than the one which wrote the poetry.lock. To avoid surprises in the reproducible build, we can specify the poetry version installed by the builder images and in the dockerfile.

Also addressed the build instructions - now that poetry shell has been deprecated, we need to revert back to invoking poetry run make.

This avoids the docker image builders breaking with:
ERROR [linux/amd64 builder 15/17] RUN poetry export -o requirements.txt --without-hashes
0.780 pyproject.toml changed significantly since poetry.lock was last generated. Run Resolving dependencies... to fix the lock file.

This occurred when the default installation version changed underneath us.

Changelog-None
@endothermicdev endothermicdev added this to the v25.05 milestone May 1, 2025
@endothermicdev endothermicdev requested a review from cdecker as a code owner May 1, 2025 20:29
endothermicdev and others added 2 commits May 1, 2025 19:20
This is required now that poetry shell is not supported

Changelog-None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants