Skip to content

release: bump version to 1.8.3#9363

Merged
radoering merged 1 commit intopython-poetry:1.8from
radoering:release/1.8.3
May 3, 2024
Merged

release: bump version to 1.8.3#9363
radoering merged 1 commit intopython-poetry:1.8from
radoering:release/1.8.3

Conversation

@radoering
Copy link
Copy Markdown
Member

Added

  • Add support for untagged CPython builds with versions ending with a + (#9207).

Changed

  • Require pkginfo>=1.10 to ensure support for packages with metadata version 2.3 (#9130).
  • Improve locking on FIPS systems (#9152).

Fixed

  • Fix an issue where unrecognized package metadata versions silently resulted in empty dependencies (#9203, #9226).
  • Fix an issue where trailing slashes in git URLs where not handled correctly (#9205).
  • Fix an issue where poetry self commands printed a warning that the current project cannot be installed (#9302).
  • Fix an issue where poetry install sporadically failed with a KeyError due to a race condition (#9335).

Docs

  • Fix incorrect information about poetry shell (#9060).
  • Add a git subdirectory example to poetry add (#9080).
  • Mention interactive credential configuration (#9074).
  • Add notes for optional advanced installation steps (#9098).
  • Add reference to configuration credentials in documentation of poetry publish (#9110).
  • Improve documentation for configuring credentials via environment variables (#9121).
  • Remove misleading wording around virtual environments (#9213).
  • Remove outdated advice regarding seeding keyring backends (#9213).
  • Add a pyproject.toml example for a dependency with multiple extras (#9138).
  • Clarify help of poetry add (#9230).
  • Add a note how to configure credentials for TestPyPI for poetry publish (#9255).
  • Fix information about the --readme option in poetry new (#9260).
  • Clarify what is special about the Python constraint in dependencies (#9256).
  • Update how to uninstall plugins via pipx (#9320).

@radoering radoering requested a review from a team April 30, 2024 17:54
@radoering radoering force-pushed the release/1.8.3 branch 2 times, most recently from 4cf80ff to 69170d5 Compare May 2, 2024 03:54
@radoering radoering merged commit e5e4b0c into python-poetry:1.8 May 3, 2024
@vfazio
Copy link
Copy Markdown
Contributor

vfazio commented May 3, 2024

looks like the release action failed with a 403 similar to ncipollo/release-action#208 :-(

@radoering
Copy link
Copy Markdown
Member Author

I know. This is probably because of some changed permissions due to #9237. Unfortunately, I do not have enough permissions to tackle this issue myself so we can only wait for someone who does. @neersighted @abn

By the way, I tested the new workflow and fixed some bugs (see #9387). However, it is not sufficient for the 1.8.3 release to fix the workflow in the main branch because it seems that the state of the workflow from the tag is used. Thus, we either have to change the workflow in the 1.8 branch and remove/reset the tag or - maybe easier - restore the permissions for the old workflow and re-run https://github.com/python-poetry/poetry/actions/runs/8940621176.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jun 4, 2024

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

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 4, 2024
@radoering radoering deleted the release/1.8.3 branch December 13, 2025 17:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants