Skip to content

Add vatsrahul1001 to the release-constraints workflow allowlist - #71152

Merged
vatsrahul1001 merged 1 commit into
mainfrom
add-rm-release-constraints-allowlist
Aug 5, 2026
Merged

Add vatsrahul1001 to the release-constraints workflow allowlist#71152
vatsrahul1001 merged 1 commit into
mainfrom
add-rm-release-constraints-allowlist

Conversation

@vatsrahul1001

@vatsrahul1001 vatsrahul1001 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

The Release constraints workflow (added in #71040) gates its build-info job on an actor allowlist. It seeded that list with the standard committer set but omitted vatsrahul1001, who is already on the allowlist of the sibling release workflows (publish-docs-to-s3.yml, release_dockerhub_image.yml, update-constraints-on-push.yml).

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines — one-line allowlist addition.

The Release constraints workflow (added in #71040) seeds its actor allowlist with the
standard committer list but omitted vatsrahul1001, who is already on the allowlist of the
sibling release workflows (publish-docs-to-s3, release_dockerhub_image,
update-constraints-on-push). As the 3.3.1 release manager he needs to dispatch this workflow;
without the entry the whole run skips (build-info gate evaluates false).

@amoghrajesh amoghrajesh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Welcome!

@vatsrahul1001 vatsrahul1001 added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label Aug 5, 2026
@vatsrahul1001
vatsrahul1001 merged commit 24c0069 into main Aug 5, 2026
6 checks passed
@vatsrahul1001
vatsrahul1001 deleted the add-rm-release-constraints-allowlist branch August 5, 2026 06:20
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-3-test PR Link

vatsrahul1001 added a commit that referenced this pull request Aug 5, 2026
…owlist (#71152) (#71153)

The Release constraints workflow (added in #71040) seeds its actor allowlist with the
standard committer list but omitted vatsrahul1001, who is already on the allowlist of the
sibling release workflows (publish-docs-to-s3, release_dockerhub_image,
update-constraints-on-push). As the 3.3.1 release manager he needs to dispatch this workflow;
without the entry the whole run skips (build-info gate evaluates false).
(cherry picked from commit 24c0069)

Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
vatsrahul1001 added a commit that referenced this pull request Aug 5, 2026
…owlist (#71152) (#71153)

The Release constraints workflow (added in #71040) seeds its actor allowlist with the
standard committer list but omitted vatsrahul1001, who is already on the allowlist of the
sibling release workflows (publish-docs-to-s3, release_dockerhub_image,
update-constraints-on-push). As the 3.3.1 release manager he needs to dispatch this workflow;
without the entry the whole run skips (build-info gate evaluates false).
(cherry picked from commit 24c0069)

Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
dabla pushed a commit to dabla/airflow that referenced this pull request Aug 14, 2026
…he#71152)

The Release constraints workflow (added in apache#71040) seeds its actor allowlist with the
standard committer list but omitted vatsrahul1001, who is already on the allowlist of the
sibling release workflows (publish-docs-to-s3, release_dockerhub_image,
update-constraints-on-push). As the 3.3.1 release manager he needs to dispatch this workflow;
without the entry the whole run skips (build-info gate evaluates false).
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-3-test Backport to v3-3-test changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants