release: bump version to 1.8.3#9363
Conversation
4cf80ff to
69170d5
Compare
|
looks like the release action failed with a 403 similar to ncipollo/release-action#208 :-( |
|
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. |
|
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. |
Added
+(#9207).Changed
pkginfo>=1.10to ensure support for packages with metadata version 2.3 (#9130).Fixed
poetry selfcommands printed a warning that the current project cannot be installed (#9302).poetry installsporadically failed with aKeyErrordue to a race condition (#9335).Docs
poetry shell(#9060).poetry add(#9080).publish(#9110).pyproject.tomlexample for a dependency with multiple extras (#9138).poetry add(#9230).poetry publish(#9255).--readmeoption inpoetry new(#9260).dependencies(#9256).pipx(#9320).