1.5.0 Release

[radoering]

This issue tracks the progress of version 1.5.0 of Poetry. Please surface any blockers or concerns you have regarding this minor release here:

Blockers

• introduce source priority supplemental
  (see Replace the secondary source type with more granular types #6713 and 6713 Introduce supplemental package source #6879 for details)
• poetry-core release release: bump version to 1.6.0 poetry-core#584
  • performance: fix a performance regression introduced in #402 poetry-core#582
• fix: installation of missing directory dependencies with --skip-directory #7923
• Changelog release: bump version to 1.5.0 #7947
• Release notes (blog) blog: announce poetry 1.5.0 website#117

Nice to have

• poetry
  • feat: let Provider use ArtifactCache #7693
  • tests: ensure forward compatibility with python-poetry/poetry-core#402 #7852
  • Add experimental POETRY_REQUESTS_TIMEOUT option #7081
  • perf: use cached file for wheel inspection #7916
• poetry-core
  • pypa packaging compliance poetry-core#402
  • support for file dependencies with subdirectories poetry-core#467

Important changes to surface

(This is intended to be the basis for the blog post and should cover new features or any manual steps/incompatibility when upgrading)

• improved source handling
  • attribute priority instead of (now deprecated) separate flags
  • 6713 Introduce explicit package source #7658
  • sources: allow to configure the priority of PyPI #7801
  • supplemental
• Poetry 1.5 will be the last (minor) version that can be run on Python 3.7.

[ralbertazzi]

Here's a tiny one you can consider including ;) #7915

[Secrus]

#7932 adding this to the list.

[dimbleby]

#7945 / #7923 would be good to fix - sad for this new function to be broken on first release.

[johnthagen]

I presume this is too big to get in for 1.5.0, but the most common bug that I see colleagues hit with Poetry these days is

• Keyring errors during non-publishing operations #1917

[dimbleby]

That issue has been open for upwards of three years. I think at this point if you care about this you probably should be assuming that the way to get it fixed is to fix it yourself ie please submit a merge request

(But I guess that even if there were a satisfactory merge request made available right now, that probably wouldn't make it into this release)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.