Fix scheduled CI upgrade check workflows failing at startup - #65168
Merged
potiuk merged 1 commit intoApr 13, 2026
Conversation
The scheduled upgrade check wrappers declared `contents: read`, which caps the permissions of the reusable `upgrade-check.yml` they call. That workflow needs `contents: write` and `pull-requests: write` to push the upgrade branch and open a draft PR, so every scheduled run failed immediately with startup_failure: The workflow is requesting 'contents: write, pull-requests: write', but is only allowed 'contents: read, pull-requests: none'. Raise the caller permissions to the ceiling required by the callee so the scheduled upgrade PR job can actually run.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
kaxil
as code owners
April 13, 2026 17:39
bugraoz93
approved these changes
Apr 13, 2026
bugraoz93
left a comment
bugraoz93
left a comment
Contributor
There was a problem hiding this comment.
Just a curious question. If I set these permissions for other CIs, it won't cause anything from forked branches to make any writes, right? This still needs 4 eyes. Additionally, let's assume it is not a scheduled job
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 13, 2026
…kflows (#65168) The scheduled upgrade check wrappers declared `contents: read`, which caps the permissions of the reusable `upgrade-check.yml` they call. That workflow needs `contents: write` and `pull-requests: write` to push the upgrade branch and open a draft PR, so every scheduled run failed immediately with startup_failure: The workflow is requesting 'contents: write, pull-requests: write', but is only allowed 'contents: read, pull-requests: none'. Raise the caller permissions to the ceiling required by the callee so the scheduled upgrade PR job can actually run. (cherry picked from commit 8291f37) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
potiuk
added a commit
that referenced
this pull request
Apr 13, 2026
…kflows (#65168) (#65176) The scheduled upgrade check wrappers declared `contents: read`, which caps the permissions of the reusable `upgrade-check.yml` they call. That workflow needs `contents: write` and `pull-requests: write` to push the upgrade branch and open a draft PR, so every scheduled run failed immediately with startup_failure: The workflow is requesting 'contents: write, pull-requests: write', but is only allowed 'contents: read, pull-requests: none'. Raise the caller permissions to the ceiling required by the callee so the scheduled upgrade PR job can actually run. (cherry picked from commit 8291f37) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Member
Author
Yep. Wokrflows from fork cannot get write access nor secrets. |
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…kflows (#65168) (#65176) The scheduled upgrade check wrappers declared `contents: read`, which caps the permissions of the reusable `upgrade-check.yml` they call. That workflow needs `contents: write` and `pull-requests: write` to push the upgrade branch and open a draft PR, so every scheduled run failed immediately with startup_failure: The workflow is requesting 'contents: write, pull-requests: write', but is only allowed 'contents: read, pull-requests: none'. Raise the caller permissions to the ceiling required by the callee so the scheduled upgrade PR job can actually run. (cherry picked from commit 8291f37) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…kflows (#65168) (#65176) The scheduled upgrade check wrappers declared `contents: read`, which caps the permissions of the reusable `upgrade-check.yml` they call. That workflow needs `contents: write` and `pull-requests: write` to push the upgrade branch and open a draft PR, so every scheduled run failed immediately with startup_failure: The workflow is requesting 'contents: write, pull-requests: write', but is only allowed 'contents: read, pull-requests: none'. Raise the caller permissions to the ceiling required by the callee so the scheduled upgrade PR job can actually run. (cherry picked from commit 8291f37) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…kflows (#65168) (#65176) The scheduled upgrade check wrappers declared `contents: read`, which caps the permissions of the reusable `upgrade-check.yml` they call. That workflow needs `contents: write` and `pull-requests: write` to push the upgrade branch and open a draft PR, so every scheduled run failed immediately with startup_failure: The workflow is requesting 'contents: write, pull-requests: write', but is only allowed 'contents: read, pull-requests: none'. Raise the caller permissions to the ceiling required by the callee so the scheduled upgrade PR job can actually run. (cherry picked from commit 8291f37) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…kflows (#65168) (#65176) The scheduled upgrade check wrappers declared `contents: read`, which caps the permissions of the reusable `upgrade-check.yml` they call. That workflow needs `contents: write` and `pull-requests: write` to push the upgrade branch and open a draft PR, so every scheduled run failed immediately with startup_failure: The workflow is requesting 'contents: write, pull-requests: write', but is only allowed 'contents: read, pull-requests: none'. Raise the caller permissions to the ceiling required by the callee so the scheduled upgrade PR job can actually run. (cherry picked from commit 8291f37) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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
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.
The scheduled upgrade-check wrappers (
scheduled-upgrade-check-main.ymlandscheduled-upgrade-check-v3-2-test.yml) declaredpermissions: contents: read, which capped the permissions of the reusableupgrade-check.ymlworkflow they call. That workflow needscontents: writeandpull-requests: writeto push the upgrade branch and open the draft PR viabreeze ci upgrade --create-pr.As a result every scheduled run since #64836 failed immediately with
startup_failure:See failing run: https://github.com/apache/airflow/actions/runs/24329934582
This raises the caller permissions in both scheduled wrappers to match the ceiling required by the callee so the upgrade PR job can actually run.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.6) following the guidelines