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.1.0a1 #2235

Merged
merged 1 commit into from
Mar 27, 2020
Merged

Release 1.1.0a1 #2235

merged 1 commit into from
Mar 27, 2020

Conversation

sdispater
Copy link
Member

This release must be downloaded via the get-poetry.py script and not via the self update command.

Changed

  • The core features of Poetry have been extracted in to a separate library: poetry-core (#2212).
  • The build backend is no longer poetry.masonry.api but poetry.core.masonry.api which requires poetry-core>=1.0.0a5 (#2212).
  • The exceptions are now beautifully displayed in the terminal with various level of details depending on the verbosity (2230).

@sdispater sdispater added the kind/release Meta-issues/PRs as part of the release process label Mar 27, 2020
@@ -1,5 +1,16 @@
# Change Log

## [1.1.0a1] - 2020-03-27

This release **must** be downloaded via the `get-poetry.py` script and not via the `self update` command.
Copy link
Member

Choose a reason for hiding this comment

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

I think this should also be documented in the README.md -- I'm afraid many people may not catch it if this information is only in the Changelog.

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think it's worth it. By the time the 1.1.0 version is out, we will have fixed it in the self update command.

And since it's a prerelease version that will not be officially announced on the website, the risk for people to accidentally update to this version is low.

@abn
Copy link
Member

abn commented Mar 27, 2020

Does this break PEP 518 support for older pyproject.toml files when requires=["poetry>=0.12"] and build-backend = "poetry.masonry.api"?

@sdispater
Copy link
Member Author

@abn No, it will still work since there is a compatibility layer here https://github.com/python-poetry/poetry/blob/develop/poetry/masonry/api.py

@sdispater sdispater merged commit 08dd8dc into develop Mar 27, 2020
@sdispater sdispater deleted the release-1.1.0a1 branch March 27, 2020 21:50
Copy link

github-actions bot commented Mar 1, 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 Mar 1, 2024
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.

3 participants