withlogicco / docker-poetry Goto Github PK

https://github.com/python-poetry/poetry/releases/tag/1.4.2

We should introduce tests ensuring that each build behaves as it should:

• Has the poetry binary available
• The poetry version installed is the one in the tag
• The poetry installation works without virtual environments

Poetry 1.4.0 was release¹, so we need to release a version in here as well.

https://github.com/python-poetry/poetry/releases/tag/1.2.1

Poetry version 1.5.0 has been released¹ and we should support it here as well.

Potry version 1.6.0 has been released¹ and we should support it here as well.

⚠️ Poetry 1.6 drops support for Python 3.7 ⚠️

Release: 1.8.1

Poetry 1.6.1 is now released¹. This should be done after #33.

Release notes: https://github.com/python-poetry/poetry/releases/tag/1.7.0

Release: https://github.com/python-poetry/poetry/releases/tag/1.7.1

Poetry version 1.5.1 has been released¹ and we should support it here as well.

This should be implemented right after #28.

https://github.com/python-poetry/poetry/releases/tag/1.4.1

We should introduce Dependabot so we get automated Pull Requests, when:

• A new stable Poetry version gets released
• New versions of our GitHub Actions get released
• (possibly) New versions of our base Docker images get released or deprecated

Python 3.12 is now released, so we should support it: https://www.python.org/downloads/release/python-3120/

Release: https://github.com/python-poetry/poetry/releases/tag/1.8.0

https://github.com/python-poetry/poetry/releases/tag/1.8.3

Release: 1.8.2

In order to get this working, we need to add the following lines in the Dockerfile

RUN python -m ensurepip --upgrade
RUN pip install --upgrade setuptools

We could consider including them in the base Dockerfile here, but IMO we should consider making sure we always have the latest version of pip and setup tools installed.