-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.2.0b2 #5725
Release 1.2.0b2 #5725
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for preparing the changelog so quickly @kasteph 🎉 👍 🥇
I don't think it is necessary to mention version bumps of dependencies, unless they introduce (important) changes to poetry.
To complete this release, the version in pyproject.toml
must be bumped as well.
Let's lock core here too. This is because we have a few changes in the next release that might not work with this pre-release. |
We should define a standard order of change log sections that we stick with. From the start of Poetry I always tried to stick to:
The rationale behind that is that I want to notify about new features and changes first. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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
version (#5715)
poetry config certificates.<repository>.cert false
(#5719virtualenvs.prompt
) to customize the prompt of the Poetry-managed virtual environment (#5606)download_file
(used when downloading dists) (#5451)--dry-run
topoetry version
command (#5603)--why
topoetry show
(#5444)dependencies via
poetry add
command (#5554)--no-cache
as a global option (#5519)--skip-existing
topoetry publish
(#2812)--all-extras
topoetry install
(#5452)poetry self
sub-commands to manage plugins and/or system environment packages, eg: keyring backends (#5450)installer.no-binary
) to allow selection of non-binary distributions when installing a dependency (#5609)Changed
poetry plugin
commands are now deprecated in favor of the more genericpoetry self
commands (#5450)
md
andrst
(#5357)specified (#5401)
experimental.system-git-client
configuration totrue
(#5428)no-pip
andno-setuptools
configuration explicit (#5455)-vv
now provides more debug information (#5503)default
tomain
(#5465)poetry export
with
poetry-plugin-export
(#5413)"null"
keyring whendisabled (#5251)
packaging
dependency to use major version 21, this change forces Poetry to drop support for managing Python 2.7 environments (#4749)Fixed
poetry update --dry-run
to not modifypoetry.lock
(#5718, #3666, #3766)path (#5688)
POETRY_CONFIG_DIR
andPOETRY_CACHE_DIR
were not being respected (#5672)gracefully (#5645)
deps (#5648)
dependencies (#4606)
poetry init -n
crashes in a root directory (#5612)constraints (#5616)
setuptools
could not be correctly installed (#5590)poetry lock --no-update
only sorted by name and not by name andversion (#5446)
package (#5403)
even markers are mutually exclusive (#4695)
poetry lock --no-update
droppedpackages (#5435)
exporting (#5156)
sources (#5362)
Docs
--readme
flag to documentation (#5357)poetry.toml
note in configuration (#5492)poetry about
,poetry help
,poetrylist
, and the--full-path
and--all
optionsdocumentation (#5664)
--why
flag (#5653)instructions (#3978, #5618)
--local
to fix issue #5623 (#5629)ZSH (#4847)
readme
option, including multiple files and additional formats (#5158)--dev-only
option (#5771)