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 1.5.0 #551

Merged
merged 3 commits into from
Jan 28, 2023
Merged

Release 1.5.0 #551

merged 3 commits into from
Jan 28, 2023

Conversation

radoering
Copy link
Member

@radoering radoering commented Jan 24, 2023

Added

  • Improve marker handling (#528, #534, #530, #546, #547).
  • Allow overriding the output directory when building dist files (#527).
  • Validate whether dependencies referenced in extras are defined in the main dependency group (#542).
  • Improve handling of generic constraints (#515).

Changed

  • Deprecate the hash function of FileDependency (#535).
  • Do not set allows_preleases implicitly anymore if the lower bound of a constraint is a pre-release (#543).
  • Poetry no longer generates a setup.py file in sdists by default (#318).
  • Remove the unused platform attribute from Package (#548).
  • Deprecate the pretty_version parameter when creating a Package (#549).
  • Validate path dependencies during use instead of during construction (#520).

Fixed

  • Fix an issue where the PEP 517 metadata_directory was not respected when building an editable wheel (#537).
  • Fix an issue where trailing newlines were allowed in tool.poetry.description (#505).
  • Fix an issue where the name of the data folder in wheels was not normalized (#532).
  • Fix an issue where the order of entries in the RECORD file was not deterministic (#545).
  • Fix an issue where parsing of VCS URLs with escaped characters failed (#524).
  • Fix an issue where the subdirectory parameter of VCS URLs was not respected (#518).
  • Fix an issue where zero padding was not correctly handled in version comparisons (#540).
  • Fix an issue where sdist builds did not support multiple READMEs (#486).

Vendoring

Copy link
Member

@Secrus Secrus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some SPAG suggestions. I'd love to have @neersighted double-check those.

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Member

@neersighted neersighted left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tweaked @Secrus's comments and added my own, everything else LGTM.

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@sonarcloud
Copy link

sonarcloud bot commented Jan 27, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
1.0% 1.0% Duplication

@neersighted neersighted merged commit b5d1934 into python-poetry:main Jan 28, 2023
@wagnerluis1982
Copy link
Contributor

Now poetry-core is released 😊, how long until main poetry gets core dependency updated?

@radoering
Copy link
Member Author

If you are referring to master: python-poetry/poetry#7423, for the release: python-poetry/poetry#7357. If you expect a specific date: as always, as long as it takes. 😉

@kpdemetriou
Copy link

@radoering This change has broken the build option in pyproject.toml. Downstream dependencies that build extensions no longer work as of poetry-core==1.5.0.

@radoering
Copy link
Member Author

@kpdemetriou Can you please be more specific? If you encountered a regression, please create an issue with the exact error message and an example to reproduce the issue.

@radoering radoering deleted the release/1.5.0 branch November 24, 2024 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants