Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade FAB to 4.1.3 #24884

Merged
merged 1 commit into from
Jul 6, 2022
Merged

Upgrade FAB to 4.1.3 #24884

merged 1 commit into from
Jul 6, 2022

Conversation

gmsantos
Copy link
Contributor

@gmsantos gmsantos commented Jul 6, 2022

No relevant changes were found when comparing airflow/www/fab_security with the FAB source.

See dpgaspar/Flask-AppBuilder@v4.1.2...v4.1.3

Ps.: I think that the constraints-main file needs to be updated somehow. Let me know if I need to handle this on that same PR.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@potiuk
Copy link
Member

potiuk commented Jul 6, 2022

You can't update constraints in the same PR because constraints are in orphaned branch (constraints-main).

The Constraints main should be refreshed at merge time via https://github.com/apache/airflow/blob/main/dev/REFRESHING_CI_CACHE.md#manually-generating-constraint-files

This is only really needed when you have the == change (or otherwise chagne that introduces range of dependency that does not overlap with the previous range). This is the only case that is not (yet) handled automatically (it could be, but we would have to create a PR automatically to the constraints-main branch and let them be merged at the same time.

Effectively it means that the person (committer) who merges it, should prepare constraints just before merge and do the push at the same time as merge (either way it needs a bit synchronized action). You cannot push to the branch as you are not a committer.

@gmsantos
Copy link
Contributor Author

gmsantos commented Jul 6, 2022

thanks for the explanation @potiuk

no relevant changes found when comparing `airflow/www/fab_security` with FAB
see dpgaspar/Flask-AppBuilder@v4.1.2...v4.1.3
@potiuk
Copy link
Member

potiuk commented Jul 6, 2022

BTW. I rebased it so that I can merge it tomorrow morning - I just merged a bit "bigger" requirement change (moving SQL classes to a new provider). So I want to make sure this one is run on -top of it.

@potiuk
Copy link
Member

potiuk commented Jul 6, 2022

But actually, you made me think - this is a good idea to bring such changes in a form of PR even if it's not automated yet.

@potiuk
Copy link
Member

potiuk commented Jul 6, 2022

Linked PR with constraints: #24886

@potiuk potiuk merged commit 01a5d8f into apache:main Jul 6, 2022
@potiuk
Copy link
Member

potiuk commented Jul 6, 2022

Both merged.

@gmsantos gmsantos deleted the bump-fab-4.1.3 branch July 7, 2022 08:34
potiuk pushed a commit to potiuk/airflow that referenced this pull request Jul 14, 2022
no relevant changes found when comparing `airflow/www/fab_security` with FAB
see dpgaspar/Flask-AppBuilder@v4.1.2...v4.1.3

(cherry picked from commit 01a5d8f)
potiuk pushed a commit to potiuk/airflow that referenced this pull request Aug 5, 2022
no relevant changes found when comparing `airflow/www/fab_security` with FAB
see dpgaspar/Flask-AppBuilder@v4.1.2...v4.1.3

(cherry picked from commit 01a5d8f)
@potiuk potiuk added this to the Airflow 2.3.4 milestone Aug 5, 2022
potiuk pushed a commit that referenced this pull request Aug 5, 2022
no relevant changes found when comparing `airflow/www/fab_security` with FAB
see dpgaspar/Flask-AppBuilder@v4.1.2...v4.1.3

(cherry picked from commit 01a5d8f)
@ephraimbuddy ephraimbuddy added the type:misc/internal Changelog: Misc changes that should appear in change log label Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:misc/internal Changelog: Misc changes that should appear in change log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants