Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: bump version to 1.3.0 #7137

Merged
merged 2 commits into from
Dec 9, 2022

Conversation

radoering
Copy link
Member

@radoering radoering commented Dec 3, 2022

Resolves: #6972

Added

  • Mark the lock file with an @generated comment as used by common tooling (#2773).
  • poetry check validates trove classifiers and warns for deprecations (#2881).
  • Introduce a top level -C, --directory option to set the working path (#6810).

Changed

  • New lock file format (version 2.0) (#6393).
  • Path dependency metadata is unconditionally re-locked (#6843).
  • URL dependency hashes are locked (#7121).
  • poetry update and poetry lock should now resolve dependencies more similarly (#6477).
  • poetry publish will report more useful errors when a file does not exist (#4417).
  • poetry add will check for duplicate entries using canonical names (#6832).
  • Wheels are preferred to source distributions when gathering metadata (#6547).
  • Git dependencies of extras are only fetched if the extra is requested (#6615).
  • Invoke pip with --no-input to prevent hanging without feedback (#6724, #6966).
  • Invoke pip with --isolated to prevent the influence of user configuration (#6531).
  • Interrogate environments with Python in isolated (-I) mode (#6628).
  • Raise an informative error when multiple version constraints overlap and are incompatible (#7098).

Fixed

  • Fix an issue where concurrent instances of Poetry would corrupt the artifact cache (#6186).
  • Fix an issue where Poetry can hang after being interrupted due to stale locking in cache (#6471).
  • Fix an issue where the output of commands executed with --dry-run contained duplicate entries (#4660).
  • Fix an issue where requests's pool size did not match the number of installer workers (#6805).
  • Fix an issue where poetry show --outdated failed with a runtime error related to direct origin dependencies (#6016).
  • Fix an issue where only the last command of an ApplicationPlugin is registered (#6304).
  • Fix an issue where git dependencies were fetched unnecessarily when running poetry lock --no-update (#6131).
  • Fix an issue where stdout was polluted with messages that should go to stderr (#6429).
  • Fix an issue with poetry shell activation and zsh (#5795).
  • Fix an issue where a url dependencies were shown as outdated (#6396).
  • Fix an issue where the source field of a dependency with extras was ignored (#6472).
  • Fix an issue where a package from the wrong source was installed for a multiple-constraints dependency with different sources (#6747).
  • Fix an issue where dependencies from different sources where merged during dependency resolution (#6679).
  • Fix an issue where experimental.system-git-client could not be used via environment variable (#6783).
  • Fix an issue where Poetry fails with an AssertionError due to distribution.files being None (#6788).
  • Fix an issue where poetry env info did not respect virtualenvs.prefer-active-python (#6986).
  • Fix an issue where poetry env list does not list the in-project environment (#6979).
  • Fix an issue where poetry env remove removed the wrong environment (#6195).
  • Fix an issue where the return code of a script was not relayed as exit code (#6824).
  • Fix an issue where the solver could silently swallow ValueError (#6790).

Docs

  • Improve documentation of package sources (#5605).
  • Correct the default cache path on Windows (#7012).

poetry-core (1.4.0)

  • The PEP 517 metadata_directory is now respected as an input to the build_wheel hook (#487).
  • ParseConstraintError is now raised on version and constraint parsing errors, and includes information on the package that caused the error (#514).
  • Fix an issue where invalid PEP 508 requirements were generated due to a missing space before semicolons (#510).
  • Fix an issue where relative paths were encoded into package requirements, instead of a file:// URL as required by PEP 508 (#512).

poetry-plugin-export (^1.2.0)

  • Ensure compatibility with Poetry 1.3.0. No functional changes.

cleo (^2.0.0)

  • Fix an issue where shell completions had syntax errors (#247).
  • Fix an issue where not reading all the output of a command resulted in a "Broken pipe" error (#165).
  • Fix an issue where errors were not shown in non-verbose mode (#166).

@radoering
Copy link
Member Author

@Secrus PTAL if we want to mention cleo.

@dimbleby
Copy link
Contributor

dimbleby commented Dec 3, 2022

python-poetry/poetry-core#487 maybe worth a mention in the poetry-core changes

IMO the cleo upgrade isn't in itself interesting, but the poetry bugs that it fixes are. These are the ones that I know about

@Secrus
Copy link
Member

Secrus commented Dec 3, 2022

@Secrus PTAL if we want to mention cleo.

I agree with Dimbleby, no need to include changelog for cleo, maybe just link to cleo changelog: https://github.com/python-poetry/cleo/blob/main/CHANGELOG.md#100---2022-11-21

@neersighted
Copy link
Member

Updated as per maintainer's call, I'm pushing a revised changelog and then we're cutting the release.

neersighted
neersighted previously approved these changes Dec 9, 2022
@neersighted neersighted merged commit aa48815 into python-poetry:master Dec 9, 2022
@yermukov
Copy link

yermukov commented Dec 11, 2022

This is update broke the whole image built and we had to go nuts to find out what actually broke it.

@neersighted
Copy link
Member

neersighted commented Dec 11, 2022

If you have discovered a showstopper regression in the release, please open a new issue with a detailed description, examples of what is going wrong, and a tested, minimal reproducer. Thank you.

@neersighted neersighted added this to the 1.3 milestone Dec 21, 2022
@neersighted neersighted added the kind/release Meta-issues/PRs as part of the release process label Dec 21, 2022
Copy link

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 Feb 29, 2024
@radoering radoering deleted the release/1.3.0 branch November 24, 2024 12:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/release Meta-issues/PRs as part of the release process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1.3.0 Release
5 participants