feat: move Poetry version ownership to poetry-lock-update

[blink1073]

What

Splits ownership of the Poetry version between the two bot actions:

• pre-commit-autoupdate now leaves the poetry hook alone (new exclude-repos input, defaulting to the poetry repo).
• poetry-lock-update now bumps the poetry hook in .pre-commit-config.yaml to the newest cooldown-eligible release (prek update --repo), reinstalls that Poetry, and regenerates poetry.lock with it. Both files land in the same PR, and the body gains a ## Poetry version section.

Why

base-setup derives CI's Poetry from the poetry hook rev. An autoupdate PR that bumped that rev silently upgraded the Poetry used to generate/check the lock, but only committed .pre-commit-config.yaml. Poetry stamps its own version into poetry.lock, so the poetry-lock hook then rewrote the lock and failed:

• the static job (pre-commit-run) with "files were modified by this hook", and
• the release dry-run, because just install runs pre-commit install and the release action's git commit tripped the same hook.

Reproduced locally; see Calysto/metakernel#495.

Notes

• get_poetry_version.py gains --repo; tests extended.
• Existing in-flight autoupdate PRs (e.g. metakernel#495) still predate this change and will stay red until the lock-update job regenerates the lock or they are recreated.

[greptile-apps]

Confidence Score: 4/5

[High risk] Moves Poetry version management into the lock-update workflow.

The PR should not merge until autoupdate reliably excludes every Poetry hook form recognized by the version helper.

Findings

1.  Poetry exclusion misses SSH URLs ▶
2.  Joint update lacks a test ▶

Summary

The PR assigns Poetry-hook updates to poetry-lock-update, which reinstalls the selected Poetry version and commits its hook revision with the regenerated lock. It also adds a default Poetry exclusion to pre-commit-autoupdate and a --repo option to the version helper.

• The default exclusion does not cover every Poetry URL form recognized by the helper.
• The joint hook-and-lock update lacks an assertion in the action tests.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A["Poetry hook rev"] --> B["base-setup: install Poetry"]
  A --> C["poetry-lock-update: update hook"]
  C --> D["Reinstall selected Poetry"]
  D --> E["Regenerate poetry.lock"]
  C --> F["Commit hook and lock in one PR"]
  E --> F
  G["pre-commit-autoupdate"] --> H["Exclude Poetry hook"]

Loading

_{Reviews (1) · Last reviewed commit: "feat: move Poetry version ownership to p..."}