You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Worker Version Upgrade fails on unrelated issues instead of skipping #1686
The Worker Version Upgrade workflow reports a failure when an issue is opened or edited without the type: worker-update label. Unrelated issue activity should skip the upgrade workflow cleanly, not produce failed runs.
Steps to reproduce
Open or edit an issue without the type: worker-update label.
The worker-version-upgrade.lock.yml workflow starts because its issue triggers include opened and edited.
The pre_activation job fails at Check worker update label.
Expected behavior
Issues without the target label are skipped without failing the workflow. Labeled worker-update issues continue through activation, subject to existing permission checks. Manual dispatch retains its existing label-check bypass.
Actual behavior
The label gate executes:
echo"$LABELS"| grep -q '"type: worker-update"'
In the observed run, LABELS was []. grep returned exit code 1, causing pre_activation to fail and all downstream jobs to be skipped. The membership check succeeded; the agent and integration tests never started.
The source documents a gh-aw compiler label-filtering workaround: names: is commented out in the generated workflow and the custom pre-activation shell step enforces the filter. That workaround turns an expected nonmatch into a hard failure.
Proposed fix and acceptance criteria
Replace the failing shell gate with a declarative label condition or another explicit non-failing skip mechanism. Edit the Markdown source and regenerate the lockfile with the pinned compiler; do not patch only the generated YAML.
Unlabeled issues and issues with unrelated labels do not activate the agent and do not fail the run.
Issues containing the exact type: worker-update label still activate, including when other labels are present.
Manual dispatch and existing membership checks retain their current behavior.
Verify the source and regenerated workflow conditions against these cases.
Activity