ci: Use --clear in uv venv for 0.10.0

[dangotbanned]

Description

Since (https://github.com/astral-sh/uv/releases/tag/0.10.0), uv now has this change:

Breaking changes

• Require --clear to remove existing virtual environments in uv venv (#17757)

  Previously, uv venv would prompt for confirmation before removing an existing virtual environment in interactive contexts, and remove it without confirmation in non-interactive contexts.
  Now, uv venv requires the --clear flag to remove an existing virtual environment. A warning for this change was added in uv 0.8.

  You can opt out of this behavior by passing the --clear flag or setting UV_VENV_CLEAR=1.

Apparently only broke the typing.yml workflow, so good news overall I guess

Related issues

• https://github.com/narwhals-dev/narwhals/actions/runs/21746636942/job/62734017631?pr=3454
• Require --clear to remove virtual environments astral-sh/uv#17757

[FBruzzesi]

Sure! Thanks @dangotbanned

[MarcoGorelli]

@dangotbanned for the future, can we use the fix label for user-facing fixes? else it ends up in the "bug fixes" part of the release notes, even though users don't need to know about it. i'd suggest the "internal" label for this one

[dangotbanned]

can we use the fix label for user-facing fixes? else it ends up in the "bug fixes" part of the release notes

@MarcoGorelli yeah sure thing!

Would it be worth adding something to the label description for those that have a special meaning?

Edit: jfc I didn't realise how big that screenshot was 😭 (shrunk it 4x now)