Skip to content

Refresh the release runner groups on release tags - #22757

Open
huydhn wants to merge 1 commit into
mainfrom
osdc/release-runner-groups-refresh
Open

huydhn wants to merge 1 commit into
mainfrom
osdc/release-runner-groups-refresh

Conversation

@huydhn

@huydhn huydhn commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Mirrors the workflow of the same name in pytorch/pytorch. On a release or release-candidate tag it reconciles the org-level release runner groups so the workflows this repository builds from stay allow-listed; on a PR touching this file, and on dispatch without the flag, it only prints the diff.

Passes --repo so the run touches only this repository's entries. The groups are shared with pytorch/pytorch, and before pytorch/test-infra#8788 the script PATCHed the allow-list to exactly one repository's desired set — the two would have removed each other's entries on every release. That landed, so this now runs against test-infra@main.

Reads RUNNER_GROUP_TOKEN from the runner-group environment. A PR run does not select that environment, so it falls back to GITHUB_TOKEN and the script takes its discovery-only path.

Verified against this repo: anchors on release/1.5, pins main, nightly, release/1.5, release/1.4 and the v1.4.1 tags. 0 workflows discovered so far, which is correct — nothing here uses a release runner label until #22753 lands, and the script refuses to apply an empty allow-list.

Authored with Claude Code.

@pytorch-bot

pytorch-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/22757

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 935498c with merge base 8011520 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@github-actions

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 11, 2026
@huydhn
huydhn marked this pull request as ready for review September 12, 2026 22:03
@huydhn
huydhn requested a review from atalman September 12, 2026 22:04
@huydhn
huydhn force-pushed the osdc/release-runner-groups-refresh branch from 78ddffd to 1952aa5 Compare September 12, 2026 22:04
@huydhn
huydhn force-pushed the osdc/release-runner-groups-refresh branch from 4e1c114 to 1952aa5 Compare September 12, 2026 23:15
@huydhn
huydhn requested a review from georgehong September 14, 2026 22:36
Mirrors pytorch/pytorch's workflow of the same name. On a release or
release-candidate tag it reconciles the org-level release runner groups so the
wheel workflows this repository builds from stay allow-listed; on a pull request
touching this file, and on dispatch without the flag, it only prints the diff.

Passes --repo so the run touches only this repository's entries. The groups are
shared with pytorch/pytorch, and before pytorch/test-infra#8788 the script
PATCHed the allow-list to exactly one repository's desired set, which would have
had the two remove each other's entries on every release.

Reads RUNNER_GROUP_TOKEN from the runner-group environment, as pytorch/pytorch
does. A pull request run does not select that environment, so it falls back to
GITHUB_TOKEN and the script takes its discovery-only path.

Authored with Claude Code.
@huydhn
huydhn force-pushed the osdc/release-runner-groups-refresh branch from 1952aa5 to 935498c Compare September 14, 2026 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. topic: not user facing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants