1.2.0 Release

Trying to gather the list of actual blockers for 1.2.0 final release. If there is a PR open that absolutely must be included in the 1.2.0 release, please link them here. Issues, unless they are deemed critical (ie. regression that fundamentally breaks workflows), are unlikely to be considered at this stage.

A link and a short note on why you think is important would suffice. If you agree that a linked issue/pr in the comments is important use 👍 else use 👎 to vote.

Let’s avoid bike shedding in here so that the maintainers can focus on the signal.

Blockers

These are a subset of the 1.2 Milestone.

• https://github.com/python-poetry/poetry-core/pull/348
• https://github.com/python-poetry/poetry/pull/5673
• https://github.com/python-poetry/poetry/pull/5450
• https://github.com/python-poetry/poetry/pull/5581
• https://github.com/python-poetry/poetry/issues/4242
• https://github.com/python-poetry/poetry-plugin-export/pull/56
• https://github.com/python-poetry/poetry/pull/5587
• https://github.com/python-poetry/poetry/pull/5590
• https://github.com/python-poetry/poetry/pull/6234
• https://github.com/python-poetry/poetry/issues/5593
• https://github.com/python-poetry/poetry/issues/5633
• https://github.com/python-poetry/poetry/issues/5675
• https://github.com/python-poetry/poetry/issues/5682
• https://github.com/python-poetry/poetry/issues/4718
• https://github.com/python-poetry/poetry/issues/5715
• https://github.com/python-poetry/poetry/issues/5727
• https://github.com/python-poetry/poetry/pull/5725
• https://github.com/python-poetry/poetry/issues/5331
• https://github.com/python-poetry/poetry/issues/6054
• https://github.com/python-poetry/poetry/issues/6184

Nice to haves

• https://github.com/python-poetry/poetry/pull/5811
• https://github.com/python-poetry/poetry/pull/5172
• https://github.com/python-poetry/poetry/pull/5451
• https://github.com/python-poetry/poetry/pull/5442
• https://github.com/python-poetry/poetry/pull/5401
• https://github.com/python-poetry/poetry/pull/5385
• https://github.com/python-poetry/poetry/pull/5718
• https://github.com/python-poetry/poetry/pull/5841
• https://github.com/python-poetry/poetry/pull/5935

General Notes

PEP 610 Changes

Due to changes required in python-poetry/poetry#5362, when upgrading from Poetry 1.1 releases, existings environments might see the following “no update” logs. This is because, with 1.2.0a1, we fixed an issue with the executor that wrote incorrect PEP 610 metadata.

  • Updating tox (3.25.0 /home/abn/.cache/pypoetry/artifacts/a2/33/48/b1983b149095eaa5fbb5f0d48841785f6778b0b3fcb8be53a7506b349a/tox-3.25.0-py2.py3-none-any.whl -> 3.25.0)
  • Updating types-requests (2.27.29 /home/abn/.cache/pypoetry/artifacts/bd/20/0d/db608c01e91c5a34cdf7f8ac0407dde334f95d16c83985b870b17f508f/types_requests-2.27.29-py3-none-any.whl -> 2.27.29)

[neersighted]

1.2.0rc1 is tagged and is in the stabilization phase. The 1.2 branch is created and will be accepting backports for any last-minute issues found with the release candidate. Assuming we don’t have any regressions, 1.2.0 will be released next Monday.

[dimbleby]

All the blockers are closed. Ship it!

Really: is there anything blocking the release, or is it “just” (yes I know) a question of maintainer time?

• If there is some blocking issue or issues, please share, perhaps someone will want to take it / them on
• If the bottleneck is maintainer time: is there anything the rest of us can do to help?