🔧 Ensure that an edit to `uv.lock` gets the `internal` label by svlandeg · Pull Request #1719 · fastapi/sqlmodel

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.

svlandeg · 2026-01-22T16:22:18Z

When dependabot pushes a sync to uv.lock, we want the internal label just like we had before when (only) requirements*.txt files were being edited. We need the internal label for the CI to pass.

YuriiMotov · 2026-01-22T16:48:25Z

As I understand it will also add internal label to PRs that update core dependencies (like Starlette version). So we will need to remove this label manually.
But I don't think this is a problem

svlandeg · 2026-01-22T17:55:09Z

I don't think so, or at least if you would edit pyproject.toml then the labeler won't add this label.