Repository navigation
Re lock uv.lock after new provider versions got stampped. - #74799
Merged
Merged
Conversation
When the version number of the providers get updated the uv.lock should be updated too as uv.lock records the version of every workspace member alongside its dependencies. For now this PR just changes this to keep the next change (that fails CI when this isn't done) small.
Member
Author
|
(I don't know if this will backport cleanly or not to v3-4-test, but it should be attempted if it does) |
josh-fell
approved these changes
Oct 15, 2026
Contributor
|
Hi maintainer, this PR was merged without a milestone set.
|
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
1 task
ashb
added
the
changelog:skip
ashb
added a commit
that referenced
this pull request
Oct 15, 2026
…#74799) (#74800) When the version number of the providers get updated the uv.lock should be updated too as uv.lock records the version of every workspace member alongside its dependencies. This is just the result of running `uv lock` on main. For now this PR just changes this to keep the next change (that fails CI when this isn't done) small. (cherry picked from commit bb14071) Co-authored-by: Ash Berlin-Taylor <ash@astronomer.io>
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 20, 2026
…#74799) (#74800) When the version number of the providers get updated the uv.lock should be updated too as uv.lock records the version of every workspace member alongside its dependencies. This is just the result of running `uv lock` on main. For now this PR just changes this to keep the next change (that fails CI when this isn't done) small. (cherry picked from commit bb14071) Co-authored-by: Ash Berlin-Taylor <ash@astronomer.io>
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
2 participants
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.
When the version number of the providers get updated the uv.lock should be
updated too as uv.lock records the version of every workspace member alongside
its dependencies.
This is just the result of running
uv lockon main.For now this PR just changes this to keep the next change (that fails CI when
this isn't done) small. i.e. #74733 should include this sort of change in future.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.