Do not fail when translation-changing commit runs as canary run #55325
Conversation
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
When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
potiuk
requested review from
amoghrajesh,
ashb,
gopidesupavan and
jedcunningham
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
shahar1
approved these changes
Sep 6, 2025
Member
Author
|
Known issue with Cloud run. Merging., |
potiuk
deleted the
fix-not-failing-translation-change-in-canary-builds
branch
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker abf06b6 v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
Member
Author
|
no backport |
mangal-vairalkar
pushed a commit
to mangal-vairalkar/airflow
that referenced
this pull request
Sep 7, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
RoyLee1224
pushed a commit
to RoyLee1224/airflow
that referenced
this pull request
Sep 8, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Sep 30, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 1, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 2, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 3, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 4, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 7, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 8, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 9, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 10, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 11, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 12, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 14, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 15, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 17, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 19, 2025
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
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 we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label).
Follow-up after #55154
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.