[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update	Pending
poetry (changelog)	1.8.4 → 1.8.5			tools	patch
python	3.13.7 → 3.15.1			tools	minor	3.15.2

---

Release Notes

python-poetry/poetry (poetry)

v1.8.5

Compare Source

Changed

• Require pkginfo>=1.12 to fix an issue with an unknown metadata version 2.4 (#​9888).
• Do not fail if the unknown metadata version is only a minor version update (#​9888).

python/cpython (python)

v3.15.1

Compare Source

v3.15.0

Compare Source

v3.14.10

Compare Source

v3.14.9

Compare Source

v3.14.8

Compare Source

v3.14.7

Compare Source

v3.14.6

Compare Source

v3.14.5

Compare Source

v3.14.4

Compare Source

v3.14.3

Compare Source

v3.14.2

Compare Source

v3.14.1

Compare Source

v3.14.0

Compare Source

v3.13.18

Compare Source

v3.13.17

Compare Source

v3.13.16

Compare Source

v3.13.15

Compare Source

v3.13.14

Compare Source

v3.13.13

Compare Source

v3.13.12

Compare Source

v3.13.11

Compare Source

v3.13.10

Compare Source

v3.13.9

Compare Source

v3.13.8

Compare Source

---

Configuration

📅 Schedule: (in timezone CET)

• 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[hashicorp-vault-sonar-prod]

Renovate Jira issue ID: BUILD-12433

[gitar-bot]

Code Review 👍 Approved with suggestions 0 closed / 1 findings

🟡 Medium risk · Updating the configured Python and Poetry tool versions could change dependency resolution or compatibility, affecting local development and CI behavior.

Bumps Poetry from 1.8.4 to 1.8.5 and Python from 3.13.7 to 3.15.1 in the mise toolchain. Approved with a suggestion: Poetry 1.8.5 does not list Python 3.15 support, so consider keeping Python on 3.13.x or upgrading Poetry to 2.5 or later alongside the interpreter (mise.toml:2-3).

💡 Edge Case: Python 3.15.1 paired with Poetry 1.8.5, which isn't supported on 3.15

📄 mise.toml:2-3

This PR moves Python from 3.13.7 to 3.15.1, two minor versions at once, but leaves Poetry on the 1.8.x line. Poetry 1.8.5 lists classifiers only up to Python 3.13 and pins poetry-core==1.9.1 (PyPI metadata). Poetry's release history shows official support for Python 3.14 arriving in 2.2.0 and for Python 3.15 in 2.5.0 (2.5.0 announcement). After this change, the mise toolchain used locally and by the build-poetry CI action pairs an interpreter with a Poetry release that was never tested on it. I didn't find a specific runtime failure for 1.8.5 on 3.15, so the risk is that this combination is unsupported, not that it is known to break. Either keep Python on a version Poetry 1.8 supports (3.13.x), or upgrade Poetry to >=2.5 along with the interpreter.

Stay on a Python version Poetry 1.8.x supports

[tools]
poetry = "1.8.5"
python = "3.13.7"

🤖 Prompt for agents

Code Review: Bumps Poetry from 1.8.4 to 1.8.5 and Python from 3.13.7 to 3.15.1 in the mise toolchain. Approved with a suggestion: Poetry 1.8.5 does not list Python 3.15 support, so consider keeping Python on 3.13.x or upgrading Poetry to 2.5 or later alongside the interpreter (`mise.toml:2-3`).

1. 💡 Edge Case: Python 3.15.1 paired with Poetry 1.8.5, which isn't supported on 3.15
   Files: mise.toml:2-3

   This PR moves Python from 3.13.7 to 3.15.1, two minor versions at once, but leaves Poetry on the 1.8.x line. Poetry 1.8.5 lists classifiers only up to Python 3.13 and pins `poetry-core==1.9.1` ([PyPI metadata](https://pypi.org/pypi/poetry/1.8.5/json)). Poetry's [release history](https://python-poetry.org/history/) shows official support for Python 3.14 arriving in 2.2.0 and for Python 3.15 in 2.5.0 ([2.5.0 announcement](https://python-poetry.org/blog/announcing-poetry-2.5.0)). After this change, the mise toolchain used locally and by the `build-poetry` CI action pairs an interpreter with a Poetry release that was never tested on it. I didn't find a specific runtime failure for 1.8.5 on 3.15, so the risk is that this combination is unsupported, not that it is known to break. Either keep Python on a version Poetry 1.8 supports (3.13.x), or upgrade Poetry to >=2.5 along with the interpreter.

   Fix (Stay on a Python version Poetry 1.8.x supports):
   [tools]
   poetry = "1.8.5"
   python = "3.13.7"

Verification Rules 2/2 met

Functional validation No results

Rules 2 passed 1 not applicable

✅ Internal artifact registries
✅ Repository license compliance

Auto-approval Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gitar-bot]

💡 Edge Case: Python 3.15.1 paired with Poetry 1.8.5, which isn't supported on 3.15

This PR moves Python from 3.13.7 to 3.15.1, two minor versions at once, but leaves Poetry on the 1.8.x line. Poetry 1.8.5 lists classifiers only up to Python 3.13 and pins poetry-core==1.9.1 (PyPI metadata). Poetry's release history shows official support for Python 3.14 arriving in 2.2.0 and for Python 3.15 in 2.5.0 (2.5.0 announcement). After this change, the mise toolchain used locally and by the build-poetry CI action pairs an interpreter with a Poetry release that was never tested on it. I didn't find a specific runtime failure for 1.8.5 on 3.15, so the risk is that this combination is unsupported, not that it is known to break. Either keep Python on a version Poetry 1.8 supports (3.13.x), or upgrade Poetry to >=2.5 along with the interpreter.

Stay on a Python version Poetry 1.8.x supports:

[tools]
poetry = "1.8.5"
python = "3.13.7"

• Apply fix

_{Check the box to apply the fix or reply for a change | Was this helpful? React with 👍 / 👎}