chore(deps): update dependency poetry to v2.3.1

[talkiq-ops]

This PR contains the following updates:

Package	Type	Update	Change
poetry (changelog)		minor	2.2.1 → 2.3.1
poetry (changelog)	pre-commit-python	minor	==2.2.1 → ==2.3.1

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

---

Release Notes

python-poetry/poetry (poetry)

v2.3.1

Compare Source

Fixed

• Fix an issue where cached information about each package was always considered outdated (#​10699).

Docs

• Document SHELL_VERBOSITY environment variable (#​10678).

v2.3.0

Compare Source

Added

• Add support for exporting pylock.toml files with poetry-plugin-export (#​10677).
• Add support for specifying build constraints for dependencies (#​10388).
• Add support for publishing artifacts whose version is determined dynamically by the build-backend (#​10644).
• Add support for editable project plugins (#​10661).
• Check requires-poetry before any other validation (#​10593).
• Validate the content of project.readme when running poetry check (#​10604).
• Add the option to clear all caches by making the cache name in poetry cache clear optional (#​10627).
• Automatically update the cache for packages where the locked files differ from cached files (#​10657).
• Suggest to clear the cache if running a command with --no-cache solves an issue (#​10585).
• Propose poetry init when trying poetry new for an existing directory (#​10563).
• Add support for poetry publish --skip-existing for new Nexus OSS versions (#​10603).
• Show Poetry's own Python's path in poetry debug info (#​10588).

Changed

• Drop support for Python 3.9 (#​10634).
• Change the default of installer.re-resolve from true to false (#​10622).
• PEP 735 dependency groups are considered in the lock file hash (#​10621).
• Deprecate poetry.utils._compat.metadata, which is sometimes used in plugins, in favor of importlib.metadata (#​10634).
• Improve managing free-threaded Python versions with poetry python (#​10606).
• Prefer JSON API to HTML API in legacy repositories (#​10672).
• When running poetry init, only add the readme field in the pyproject.toml if the readme file exists (#​10679).
• Raise an error if no hash can be determined for any distribution link of a package (#​10673).
• Require dulwich>=0.25.0 (#​10674).

Fixed

• Fix an issue where poetry remove did not work for PEP 735 dependency groups with include-group items (#​10587).
• Fix an issue where poetry remove caused dangling include-group references in PEP 735 dependency groups (#​10590).
• Fix an issue where poetry add did not work for PEP 735 dependency groups with include-group items (#​10636).
• Fix an issue where PEP 735 dependency groups were not considered in the lock file hash (#​10621).
• Fix an issue where wrong markers were locked for a dependency that was required by several groups with different markers (#​10613).
• Fix an issue where non-deterministic markers were created in a method used by poetry-plugin-export (#​10667).
• Fix an issue where wrong wheels were chosen for installation in free-threaded Python environments if Poetry itself was not installed with free-threaded Python (#​10614).
• Fix an issue where poetry publish used the metadata of the project instead of the metadata of the build artifact (#​10624).
• Fix an issue where poetry env use just used another Python version instead of failing when the requested version was not supported by the project (#​10685).
• Fix an issue where poetry env activate returned the wrong command for dash (#​10696).
• Fix an issue where data-dir and python.installation-dir could not be set (#​10595).
• Fix an issue where Python and pip executables were not correctly detected on Windows (#​10645).
• Fix an issue where invalid template variables in virtualenvs.prompt caused an incomprehensible error message (#​10648).

Docs

• Add a warning about ~/.netrc for Poetry credential configuration (#​10630).
• Clarify that the local configuration takes precedence over the global configuration (#​10676).
• Add an explanation in which cases packages are automatically detected (#​10680).

poetry-core (2.3.0)

• Normalize versions (#​893).
• Fix an issue where unsatisfiable requirements did not raise an error (#​891).
• Fix an issue where the implicit main group did not exist if it was explicitly declared as not having any dependencies (#​892).
• Fix an issue where python_full_version markers with pre-release versions were parsed incorrectly (#​893).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions]

Approved 👍

[gemini-code-assist]

Summary of Changes

Hello @talkiq-ops, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the poetry pre-commit hook to version 2.3.0. This upgrade ensures that the project's pre-commit checks utilize the latest capabilities and best practices provided by Poetry, incorporating new features, improvements, and bug fixes, while also aligning with the updated Python version support.

Highlights

• Pre-commit Hook Update: The poetry pre-commit hook has been updated from version 2.2.1 to 2.3.0 in the .pre-commit-config.yaml file.
• Poetry v2.3.0 Major Changes: Poetry version 2.3.0 introduces significant changes, including dropping support for Python 3.9 and altering the default behavior of installer.re-resolve from true to false.
• New Features in Poetry v2.3.0: This new Poetry version adds support for exporting pylock.toml files, specifying build constraints for dependencies, and publishing artifacts with dynamically determined versions, among other enhancements.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the poetry pre-commit hook from version 2.2.1 to 2.3.0. This is a breaking change, as poetry 2.3.0 drops support for Python 3.9, which this project still supports. This will cause the pre-commit hook to fail in any environment running Python 3.9. I have added a critical comment suggesting a fix.

[gemini-code-assist]

Updating poetry to version 2.3.0 will break the pre-commit hook for environments using Python 3.9. According to the release notes, poetry 2.3.0 has dropped support for Python 3.9. Since this project supports Python 3.9 (as defined in all pyproject.toml files), this change will cause pre-commit to fail for developers or CI environments running on Python 3.9.

To fix this, you can either:

1. Revert this change to keep using poetry==2.2.1.
2. Add language_version: python3.10 (or a newer version) to this pre-commit hook definition in .pre-commit-config.yaml to ensure it runs with a compatible Python version.

I'm suggesting reverting for now as it's the simplest fix.

        - poetry==2.2.1