Copilot · GitHub

Copilot AI linked an issue

Aug 7, 2026

that may be closed by this pull request

Closed

…requests
Co-authored-by: dsyme <7204669+dsyme@users.noreply.github.com>

Copilot AI changed the title [WIP] Fix add labels safe output failure on invalid GraphQL mutation Fix add_labels issue-intent path failing on pull requests

Aug 7, 2026

pelikhan

@pelikhan

pelikhan marked this pull request as ready for review

August 7, 2026 19:38

Copilot AI balanced review requested due to automatic review settings

August 7, 2026 19:38
…tions
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

github-actions[bot]

Open

github-actions[bot]

github-actions[bot]

Closed

github-actions[bot]

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

@github-actions

Closed

…s-safe-output-failure
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>

@pelikhan

@pelikhan

pelikhan deleted the copilot/fix-add-labels-safe-output-failure branch

August 7, 2026 20:55

oliviamazzotta47-lab

Closed

This was referenced

Aug 7, 2026

Closed

Closed

Merged

3 tasks

xirzec added a commit to Azure/azure-sdk-for-js that referenced this pull request

Aug 17, 2026
### Packages impacted by this PR
None.
### Issues associated with this PR
Copilot CLI launch failures caused by the v0.85.4
`/usr/local/bin/copilot` hardcoded path:
- Fixes #39564
- Fixes #39586
- Fixes #39600
- Fixes #39609
- Fixes #39619
- Fixes #39623
- Fixes #39624
- Fixes #39625
- Fixes #39628
Management review `add_labels` failures caused by sending pull request
node IDs through the issue-only GraphQL intent mutation:
- Fixes #39557
- Fixes #39608
- Fixes #39610
- Fixes #39611
### Describe the problem that is addressed by this PR
The repository pinned gh-aw v0.85.4. Recent GitHub-hosted runners can
satisfy the Copilot CLI install from the tool cache without creating
`/usr/local/bin/copilot`, but v0.85.4-generated workflows invoke that
hardcoded path and fail with `spawn /usr/local/bin/copilot ENOENT`.
The pinned safe-output implementation also routes intent-aware
`add_labels` calls for pull requests through the issue-only
`updateIssue` mutation, causing `Could not resolve to Issue node`
failures.
This PR:
- Updates gh-aw setup and action pins from v0.85.4 to v0.86.2.
- Recompiles all 12 agentic workflows with the v0.86.2 Copilot binary
staging logic.
- Picks up the v0.86.2 pull-request label fallback to the REST API.
- Refreshes workflow action references, container pins, and the
agentic-workflows dispatcher skill.
- Explicitly disables Bash in `issue-triage`, as required by the newer
strict compiler when GitHub tool integrity filtering is disabled.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
Used the standard `gh aw upgrade` path rather than hand-editing
generated lockfiles. This incorporates the upstream fixes and keeps
every generated workflow consistent with the pinned compiler and action
versions.
### Are there test cases added in this PR? _(If not, why?)_
No. This is a tooling upgrade validated by recompiling all 12 workflows
successfully. The regenerated locks no longer reference
`/usr/local/bin/copilot` and instead stage the resolved binary through
`GH_AW_COPILOT_BIN`.
### Provide a list of related PRs _(if any)_
- Copilot tool-cache fix: github/gh-aw#52464
- Pull-request label fix: github/gh-aw#51168
- Prior v0.86.2 recompilation confirming the Copilot fix:
github/gh-aw-threat-detection#849
### Checklists
- [ ] Added impacted package name to the issue description. _(N/A: no
SDK package changes.)_
- [ ] Does this PR need any fixes in the SDK Generator? _(No.)_
- [ ] Added a changelog (if necessary). _(N/A: tooling-only change.)_
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 9461f557-23d2-4e94-af97-ca02a60d2402

Read the original on github.com ↗