Refresh uv.lock and Edge OpenAPI spec after #67093 env upgrade#67188
Merged
Conversation
After #67093 upgraded the CI environment (.pre-commit-config.yaml, uv.lock, dev/breeze/uv.lock), the prek hook generate-openapi-spec-edge fails on every PR running full static checks because the committed v2-edge-generated.yaml is stale relative to the regenerated output. The drift is a description string on the TaskInstanceDTO schema. Regenerate to unblock all currently-open PRs.
4ce691c to
b5239e9
Compare
jscheffl
approved these changes
May 19, 2026
This was referenced May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three independent drifts that surfaced as
files were modified by hookon every open PR running fullCI image checks / Static checks:Edge worker OpenAPI yaml (
providers/edge3/.../v2-edge-generated.yaml): theTaskInstanceDTOdescription string is stale relative to the source docstring atairflow-core/src/airflow/executors/workloads/task.py:62-64. The drift was introduced by Introduce BaseTaskInstanceDTO and duplicate it across core and task-sdk #67174 ("Introduce BaseTaskInstanceDTO and duplicate it across core and task-sdk"), which split the class but didn't regenerate the edge3 yaml. Pure description-string change — no schema, property, or required-field changes; no API contract break.uv.lock
ci-imagedev-dependency group: catches up to the[dependency-groups.ci-image]block added by Aggregate CI-image dependency groups #67130 (which didn't refresh the lockfile).pyproject.toml:1380already defines the group; this PR just materializes it inuv.lock.uv.lock
secretstoragemarkers: normalized byuv 0.11.14(bumped by [main] Upgrade important CI environment #67093 "[main] Upgrade important CI environment"). The new compound markers are a disjoint disjunction-of-conjunctions rewrite — semantically equivalent for all common platforms (linux, darwin-arm64, darwin-x86_64); the added emscripten/win32 clauses are explicit normalization, not a behavior change.Unblocks #66574, #67184, #67180 and any other open PR running full Static checks.
Regenerated locally inside Breeze via:
PATH=".venv/bin:$PATH" prek run generate-openapi-spec-edge --all-filesuv lock --refreshDiff is +64/−4 across 2 files. No code change.