Bump poetry from 1.8.5 to 2.0.0 in /.github/workflows

[dependabot]

Bumps poetry from 1.8.5 to 2.0.0.

Release notes

Sourced from poetry's releases.

2.0.0

Added

• Add support for the project section in the pyproject.toml file according to PEP 621 (#9135, #9917).
• Add support for defining Poetry plugins that are required by the project and automatically installed if not present (#9547).
• Lock resulting markers and groups and add a installer.re-resolve option (default: true) to allow installation without re-resolving (#9427).
• Add a --local-version option to poetry build (#9064).
• Add a --clean option to poetry build (#9067).
• Add FIPS support for poetry publish (#9101).
• Add the option to use poetry new interactively and configure more fields (#9101).
• Add a config option installer.only-binary to enforce the use of binary distribution formats (#9150).
• Add support for poetry search in legacy sources (#9132).
• Add support to resume downloads from connection resets (#9422).
• Add the option to define a constraint for the required Poetry version to manage the project (#9547).
• Add an --all-groups option to poetry install (#9744).
• Add an poetry env activate command as replacement of poetry shell (#9763).
• Add a --markers option to poetry add to add a dependency with markers (#9814).
• Add a --migrate option to poetry config to migrate outdated configs (#9830).
• Add a --project option to search the pyproject.toml file in another directory without switching the directory (#9831).
• Add support for shortened hashes to define git dependencies (#9748).
• Add partial support for conflicting extras (#9553).
• Add a poetry sync command as replacement of poetry install --sync (#9801).

Changed

• Change the default behavior of poetry lock to --no-update and introduce a --regenerate option for the old default behavior (#9327).
• Remove the dependency on poetry-plugin-export so that poetry export is not included per default (#5980).
• Outsource poetry shell into poetry-plugin-shell (#9763).
• Change the interface of poetry add --optional to require an extra the optional dependency is added to (#9135).
• Actually switch the directory when using --directory/-C (#9831).
• Drop support for Python 3.8 (#9692).
• Rename experimental.system-git-client to experimental.system-git (#9787, #9795).
• Replace virtualenvs.prefer-active-python by the inverse setting virtualenvs.use-poetry-python and prefer the active Python by default (#9786).
• Deprecate several fields in the tool.poetry section in favor of the respective fields in the project section in the pyproject.toml file (#9135).
• Deprecate poetry install --sync in favor of poetry sync (#9801).
• Upgrade the warning if the current project cannot be installed to an error (#9333).
• Remove special handling for platformdirs 2.0 macOS config directory (#8916).
• Tweak PEP 517 builds (#9094).
• Use Poetry instead of pip to manage dependencies in isolated build environments (#9168, #9227).
• Trust empty Requires-Dist with modern metadata (#9078).
• Do PEP 517 builds instead of parsing setup.py to determine dependencies (#9099).
• Drop support for reading lock files prior version 1.0 (created with Poetry prior 1.1) (#9345).
• Default to >= instead of ^ for the Python requirement when initializing a new project (#9558).
• Limit build-system to the current major version of poetry-core when initializing a new project (#9812).
• Remove pip-based installation, i.e. installer.modern-installation = false (#9392).
• Remove virtualenvs.options.no-setuptools config option and never include setuptools per default (#9331).
• Rename exceptions to have an Error suffix (#9705).
• Remove deprecated CLI options and methods and revoke the deprecation of --dev (#9732).
• Ignore installed packages during dependency resolution (#9851).
• Improve the error message on upload failure (#9701).

... (truncated)

Changelog

Sourced from poetry's changelog.

[2.0.0] - 2025-01-05

Added

• Add support for the project section in the pyproject.toml file according to PEP 621 (#9135, #9917).
• Add support for defining Poetry plugins that are required by the project and automatically installed if not present (#9547).
• Lock resulting markers and groups and add a installer.re-resolve option (default: true) to allow installation without re-resolving (#9427).
• Add a --local-version option to poetry build (#9064).
• Add a --clean option to poetry build (#9067).
• Add FIPS support for poetry publish (#9101).
• Add the option to use poetry new interactively and configure more fields (#9101).
• Add a config option installer.only-binary to enforce the use of binary distribution formats (#9150).
• Add backend support for legacy repository search (#9132).
• Add support to resume downloads from connection resets (#9422).
• Add the option to define a constraint for the required Poetry version to manage the project (#9547).
• Add an --all-groups option to poetry install (#9744).
• Add an poetry env activate command as replacement of poetry shell (#9763).
• Add a --markers option to poetry add to add a dependency with markers (#9814).
• Add a --migrate option to poetry config to migrate outdated configs (#9830).
• Add a --project option to search the pyproject.toml file in another directory without switching the directory (#9831).
• Add support for shortened hashes to define git dependencies (#9748).
• Add partial support for conflicting extras (#9553).
• Add a poetry sync command as replacement of poetry install --sync (#9801).

Changed

• Change the default behavior of poetry lock to --no-update and introduce a --regenerate option for the old default behavior (#9327).
• Remove the dependency on poetry-plugin-export so that poetry export is not included per default (#5980).
• Outsource poetry shell into poetry-plugin-shell (#9763).
• Change the interface of poetry add --optional to require an extra the optional dependency is added to (#9135).
• Actually switch the directory when using --directory/-C (#9831).
• Drop support for Python 3.8 (#9692).
• Rename experimental.system-git-client to experimental.system-git (#9787, #9795).
• Replace virtualenvs.prefer-active-python by the inverse setting virtualenvs.use-poetry-python and prefer the active Python by default (#9786).
• Deprecate several fields in the tool.poetry section in favor of the respective fields in the project section in the pyproject.toml file (#9135).
• Deprecate poetry install --sync in favor of poetry sync (#9801).
• Upgrade the warning if the current project cannot be installed to an error (#9333).
• Remove special handling for platformdirs 2.0 macOS config directory (#8916).
• Tweak PEP 517 builds (#9094).
• Use Poetry instead of pip to manage dependencies in isolated build environments (#9168, #9227).
• Trust empty Requires-Dist with modern metadata (#9078).
• Do PEP 517 builds instead of parsing setup.py to determine dependencies (#9099).
• Drop support for reading lock files prior version 1.0 (created with Poetry prior 1.1) (#9345).
• Default to >= instead of ^ for the Python requirement when initializing a new project (#9558).
• Limit build-system to the current major version of poetry-core when initializing a new project (#9812).
• Remove pip-based installation, i.e. installer.modern-installation = false (#9392).
• Remove virtualenvs.options.no-setuptools config option and never include setuptools per default (#9331).
• Rename exceptions to have an Error suffix (#9705).

... (truncated)

Commits

• 8cad7a4 release: bump version to 2.0.0
• 714c024 chore: update dependencies and fix warnings (#9933)
• b9646bd Remove outdated poetry lock --no-update suggestion (#9936)
• d9f1914 ci: use current vercel version (#9926)
• 756e1a3 introduce sync command and deprecate install --sync (#9801)
• 2d540ea chore: update github actions (#9922)
• a7079ac remove: improve error message when trying to remove a package from a project ...
• 2da550a PEP 621: fix poetry source add if there is no tool.poetry section yet (#9...
• 625f42e fix: properly close streaming requests when not completely consumed (#9899)
• 21e30b1 docs: fix "introduced version" for installer.only-binary and make headings ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.