[v3-3-test] Add vatsrahul1001 to the release-constraints workflow allowlist (#71152) - #71153
Merged
Merged
Conversation
…owlist (#71152) 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>
1 task
vatsrahul1001
marked this pull request as ready for review
August 5, 2026 06:22
vatsrahul1001
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
August 5, 2026 06:22
vatsrahul1001
added
the
changelog:skip
vatsrahul1001
approved these changes
Aug 5, 2026
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>
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
1 participant
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 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