Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Jul 21, 2025

We sometimes want to build airflow docs from tip of the branch - and in this case we should be able to override the version we are building rather than deriving it from the TAG.


^ 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 airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Jul 21, 2025
@potiuk potiuk force-pushed the allow-to-release-airflow-from-branch branch from 632a9a3 to 9b08fde Compare July 21, 2025 10:31
We sometimes want to build airflow docs from tip of the branch - and in
this case we should be able to override the version we are building
rather than deriving it from the TAG.
@potiuk potiuk force-pushed the allow-to-release-airflow-from-branch branch from 9b08fde to 3b5de10 Compare July 21, 2025 10:33
@potiuk potiuk requested review from eladkal and kaxil July 21, 2025 10:34
@potiuk
Copy link
Member Author

potiuk commented Jul 21, 2025

Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it!

@potiuk potiuk merged commit c12aea3 into main Jul 21, 2025
105 checks passed
@potiuk potiuk deleted the allow-to-release-airflow-from-branch branch July 21, 2025 13:11
@github-actions
Copy link

Backport failed to create: v3-0-test. View the failure log Run details

Status Branch Result
v3-0-test Commit Link

You can attempt to backport this manually by running:

cherry_picker c12aea3 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

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

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants