Skip to content

Conversation

@github-actions
Copy link

(cherry picked from commit 8615b55)

Co-authored-by: Elad Kalif 45845474+eladkal@users.noreply.github.com

(cherry picked from commit 8615b55)

Co-authored-by: Elad Kalif <45845474+eladkal@users.noreply.github.com>
@eladkal eladkal marked this pull request as ready for review September 30, 2025 12:57
@eladkal eladkal merged commit ac730ee into v3-1-test Sep 30, 2025
94 of 97 checks passed
@eladkal eladkal deleted the backport-8615b55-v3-1-test branch September 30, 2025 14:06
@gopidesupavan
Copy link
Member

we need to update the projecttoml files in the respective providers, because we build image from the branch and using it. it seems now the image build failing on v3-1

https://github.com/apache/airflow/actions/runs/18134768097/job/51611661627?pr=56255#step:11:14741

@gopidesupavan
Copy link
Member

@eladkal one option is updating directly providers version in toml files on v3-1 or backporting the provider release PR from main to v3-1

@potiuk
Copy link
Member

potiuk commented Oct 1, 2025

Yes. @gopidesupavan is right @eladkal - this one causes v3-1-test to fail. Until we remove providers from v3-* branches you cannot limit the providers in to-be-released version of airflow without also synchroinizing version of providers in that branch. This is one of the things that removing providers from "release" branch will make possible (when we do it as preparation to potential splitting providers out).

Currently, in order to build CI image, pyproject.toml and dependencies in v3--test branch are used from sources (this is how workspace works and how we worked even before workspaces) - and until we change the approach, we need to bump the versions in v3--test branches if we we want to bump them in preinstalled depencies.

Another option is to modify workspace definition and remove the preinstalled providers from the workspace. That might also work as in this case the image will install the providers from PyPI (and that's how we are going to address provider's removal from v3-* branches). But it might not work out-of-the-box.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants