-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Add documentation and release policy on "latest" constraints #21093
Add documentation and release policy on "latest" constraints #21093
Conversation
8621fc6
to
8fdd083
Compare
8fdd083
to
df194c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @potiuk for taking care of this. It really helps my use case!
The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
@jedcunningham - I am merging this one, but if we want to correct it, happy to do it (I just want to cherry-pick it to 2-2-test so that it finds its way to the docs :) |
BTW. I already created the "constraints-latest" tag for 2.2.3: https://raw.githubusercontent.com/apache/airflow/constraints-latest/constraints-3.7.txt |
(cherry picked from commit aac5a1d)
(cherry picked from commit aac5a1d)
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.