Update dependency poetry to v2 #1319
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/poetry-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.8.5
->2.0.0
Release Notes
python-poetry/poetry (poetry)
v2.0.0
Compare Source
Added
project
section in thepyproject.toml
file according to PEP 621 (#9135,#9917).
installer.re-resolve
option (default:true
) to allow installation without re-resolving (#9427).--local-version
option topoetry build
(#9064).--clean
option topoetry build
(#9067).poetry publish
(#9101).poetry new
interactively and configure more fields (#9101).installer.only-binary
to enforce the use of binary distribution formats (#9150).--all-groups
option topoetry install
(#9744).poetry env activate
command as replacement ofpoetry shell
(#9763).--markers
option topoetry add
to add a dependency with markers (#9814).--migrate
option topoetry config
to migrate outdated configs (#9830).--project
option to search thepyproject.toml
file in another directory without switching the directory (#9831).poetry sync
command as replacement ofpoetry install --sync
(#9801).Changed
poetry lock
to--no-update
and introduce a--regenerate
option for the old default behavior (#9327).poetry-plugin-export
so thatpoetry export
is not included per default (#5980).poetry shell
intopoetry-plugin-shell
(#9763).poetry add --optional
to require an extra the optional dependency is added to (#9135).--directory
/-C
(#9831).experimental.system-git-client
toexperimental.system-git
(#9787, #9795).virtualenvs.prefer-active-python
by the inverse settingvirtualenvs.use-poetry-python
and prefer the active Python by default (#9786).tool.poetry
section in favor of the respective fields in theproject
section in thepyproject.toml
file (#9135).poetry install --sync
in favor ofpoetry sync
(#9801).platformdirs 2.0
macOS config directory (#8916).#9227).
Requires-Dist
with modern metadata (#9078).setup.py
to determine dependencies (#9099).>=
instead of^
for the Python requirement when initializing a new project (#9558).build-system
to the current major version ofpoetry-core
when initializing a new project (#9812).installer.modern-installation = false
(#9392).virtualenvs.options.no-setuptools
config option and never includesetuptools
per default (#9331).Error
suffix (#9705).--dev
(#9732).poetry show <package>
(#9750).crashtest
(#9108).keyring>=23.3.1
(#9167).build>=1.2.1
(#9283).dulwich>=0.22.6
(#9748).Fixed
poetry env remove
failed ifvirtualenvs.in-project
was set totrue
(#9118).poetry add
resulted in a brokenpyproject.toml
(#9277).envs.toml
(#9286).poetry build --directory
(#9433).poetry install
without an existing lock file (#9345).poetry-check
pre-commit hook did not trigger if onlypoetry.lock
has changed (#9504).virtualenvs.prefer-active-python
was not respected (#9278).direct_url.json
with vcs URLs not compliant with PEP 610 was written (#9007).installer.max-workers
was ignored for the implicit PyPI source (#9815).poetry.toml
) were ignored for the implicit PyPI source (#9816).dulwich
versions resulted in different hashes for a git dependency from a tag (#9849).IndexError
(#9505).allow-prereleases = false
still allowed pre-releases if no other solution was found (#9798).poetry check
falsely reported that an invalid source "pypi" is referenced in dependencies (#9475).poetry install --sync
tried to uninstall system site packages if the virtual environment was created withvirtualenvs.options.system-site-packages = true
(#9863).Docs
pre-commit-autoupdate
as an alternative topre-commit autoupdate
(#9716).exclude
andinclude
(#9734).~=
(#9783).poetry-core (
2.0.0
)platform_release
marker (#722).in
/not in
in generic constraints (#722).SOURCE_DATE_EPOCH
when building packages (#766,#781).
METADATA
files with version 2.3 instead of 2.2 (#707).x
in version constraints (#770).#769).
tool.poetry.dev-dependencies
in favor oftool.poetry.group.dev.dependencies
(#754).platlib
directory of the wrong Python was used (#726).+
was not allowed in git URL paths (#765).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.