1.2.0 Release

[abn]

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.

• Release 1.1.0b1 poetry-core#348
• update poetry-core to 1.1.0b1 #5673
• replace poetry plugin commands with more generic poetry self commands #5450
• improve git http authentication via repository configuration #5581
• Poetry tries to remove setuptools and then complains it can't find it #4242
• Release 1.0.2 poetry-plugin-export#56
• Rename implicit group "default" to "main" (poetry-plugin-export version bump) #5587
• ensure setup.py editable builds do not use pep517 #5590
• Remove mentions of Python 2.7 from docs #6234
• union of multi-markers is broken #5593
• Cache clear fails without waiting for input #5633
• Remove tomlkit regression mitigation #5675
• Current master falls back to PyPi when using private repo. #5682
• AttributeError when adding a dependency group when private repo present (Poetry 1.2.0a2) #4718
• Support for multiple-constraint direct origin dependencies with same version #5715
• poetry add "requests[security]" fails on Poetry 1.2.0b1 #5727
• Release 1.2.0b2 #5725
• Unable to create Virtual Environment with MS Store Python #5331
• poetry 1.2.0b3 lock fails with no output #6054
• Locked hash of VCS dependency with extras is ignored when installing #6184

Nice to haves

• Fix for url zip subdirectories #5811
• Fix for git subdirectories #5172
• add progress to download_file if in Indicator context #5451
• add prefetching of index in PEP503 repositories #5442
• build.script: use build environment for execution #5401
• Prefer compatible wheels over source distribution for legacy repository dependency resolution #5385
• Ensure --dry-run option doesn't update poetry.lock for add, update and remove #5718
• Add support for yanked releases and files (PEP-592) #5841
• Use dulwich to fetch global and local git config #5935

General Notes

PEP 610 Changes

Due to changes required in #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]

I would like to get #5479 or a successor in -- I have yet to look closely to validate the approach, but I think a 1.2 release should solve the underlying issue (#4678), and the root cause shouldn't be too gory.

[matteosantama]

#4979 was deemed a duplicate and closed, but it is different in that it represents a 1.1.x -> 1.2.x regression. As far as I can tell, build scripts will be broken by 1.2.0

[Secrus]

I'd say this: #5529, as big update like this, is good moment to remove 2.7 support. Still working on it though.

[Secrus]

#5633 this should be fixed before release

[mkniewallner]

#3767 may be really nice to have too.

[fsgnil]

Hey folks,

My company is very interested in using poetry as part of our python infrastructure. We have been trying poetry internally and feeling really good about it. The problem is that we need to use poetry plugin to support some of our internal pypi set up. So I'm wondering if there is an estimated release date for poetry 1.2.0.

Thanks!

[neersighted]

Hey folks,

My company is very interested in using poetry as part of our python infrastructure. We have been trying poetry internally and feeling really good about it. The problem is that we need to use poetry plugin to support some of our internal pypi set up. So I'm wondering if there is an estimated release date for poetry 1.2.0.

Thanks!

As with most solely voulenteer-driven projects, the answer is unfortunately when it's ready. The 1.2 release is quite big due to our poor release cadence, so this is taking a decent amount of time to cook. We hope to have a RC out in a week or two, and have a final release a week after that. Setbacks like major regressions or complications in the final few blockers may affect that timeline.

If you are interested in helping us get over the finish line, we're always looking for additional help. I'd suggest joining our Discord server and asking if there's anything you can help with in #contributing -- in particular, we're still looking for more volunteers for triage, as well as product/release management.

[fsgnil]

Thanks for the quick reply.

I'll see if I can contribute too.

Hi there, absolutely love poetry. Would it imply a lot of extra work (wasted volunteer time) to release more beta's while the final release is still blocked? There are several fixes in the master branch which are not in 1.2.0b1, so to use those I would have to install poetry from source, rather than using the install script with --preview.

[abn]

@wvzytlyn we do plan on releasing a new beta this week (hopefully). The short answer to your question is, right now it does still take effort to get a new beta out because we need some manual work (changelogs, testing etc).

While releasing often might be good, right now due to the amount of folks using 1.2.0b1 in production workflows, it might pose a larger issue if we release with known breakages.

Let's keep this issue clear of such discussions. Feel free to ping us on discord or raise discussion on GH.

[yodaldevoid]

As get-poetry.py is getting depreciated with 1.2.0, I'd ask that #5331 be added as a blocker as currently some people are unable to install poetry on Windows with the new installer.

[Darsstar]

I would like to see #5727 fixed. I posted working code in the issue, so now I get to dive in the test cases for solving in order to be a good open source citizen and provide a failing test case.

[neersighted]

As get-poetry.py is getting depreciated with 1.2.0, I'd ask that #5331 be added as a blocker as currently some people are unable to install poetry on Windows with the new installer.

See my comments on that issue -- I don't think we're going to call this a blocker, but I would like to see MS Store Python working before we ship 1.2 if it's not going to hold up the whole release. The issue likely lies in the installer which means it can be fixed after release with no additional patch, anyway.