Refresh agentic workflows to gh-aw v0.83.1; issue-intent on issue-triage#2063
Open
alondahari wants to merge 10 commits into
Open
Refresh agentic workflows to gh-aw v0.83.1; issue-intent on issue-triage#2063alondahari wants to merge 10 commits into
alondahari wants to merge 10 commits into
Conversation
Refresh the repo's GitHub Agentic Workflows from gh-aw v0.82.10 to the latest stable release v0.82.14 (no pre-releases). Recompiles the 11 existing AW workflows with the stable compiler and bumps the pinned setup-cli/setup action and version references. No source .md workflows were changed; all frontmatter/body hashes are byte-identical, so triggers, permissions, tools, safe outputs, network, prompts, and engine are unchanged. Only generated/runtime output differs (compiler stamp, bundled copilot engine 1.0.70->1.0.71, action pins, image digests). Refs github/plan-track-agentic-toolkit#516 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
Contributor
There was a problem hiding this comment.
Pull request overview
Updates all agentic workflows from gh-aw v0.82.10 to stable v0.82.14.
Changes:
- Updates pinned gh-aw actions and verification tooling.
- Regenerates 11 workflow locks with newer runtime dependencies.
- Preserves source workflow hashes, but the upgraded runtime introduces behavior changes that the PR description should acknowledge.
Show a summary per file
| File | Description |
|---|---|
.github/aw/actions-lock.json |
Updates gh-aw action pins. |
.github/workflows/agentics-maintenance.yml |
Refreshes generated maintenance workflow. |
.github/workflows/copilot-setup-steps.yml |
Updates cloud-agent gh-aw setup. |
.github/workflows/verify-compiled.yml |
Verifies locks using v0.82.14. |
.github/workflows/cross-repo-issue-analysis.lock.yml |
Regenerates cross-repository analysis workflow. |
.github/workflows/handle-bug.lock.yml |
Regenerates bug handler. |
.github/workflows/handle-documentation.lock.yml |
Regenerates documentation handler. |
.github/workflows/handle-enhancement.lock.yml |
Regenerates enhancement handler. |
.github/workflows/handle-question.lock.yml |
Regenerates question handler. |
.github/workflows/issue-classification.lock.yml |
Regenerates issue classifier. |
.github/workflows/issue-triage.lock.yml |
Regenerates issue triage workflow. |
.github/workflows/java-adapt-handwritten-code-to-accept-upgrade-changes.lock.yml |
Regenerates Java adaptation workflow. |
.github/workflows/java-codegen-fix.lock.yml |
Regenerates Java codegen fixer. |
.github/workflows/release-changelog.lock.yml |
Regenerates changelog workflow. |
.github/workflows/sdk-consistency-review.lock.yml |
Regenerates SDK consistency review. |
Review details
- Files reviewed: 15/15 changed files
- Comments generated: 1
- Review effort level: Medium
| - name: Setup Scripts | ||
| id: setup | ||
| uses: github/gh-aw-actions/setup@05205436a78512d71a2d842e46586ed05f4fa058 # v0.82.10 | ||
| uses: github/gh-aw-actions/setup@b6d1443e05b8716267fa19425b99aa4f12006b4a # v0.82.14 |
Change the target from stable v0.82.14 to pre-release v0.83.0 per updated request. Recompiles the same 11 AW workflows with the v0.83.0 compiler and bumps the pinned setup-cli/setup action and version references. Behavior unchanged: no source .md edited; all 11 locks keep byte-identical frontmatter/body hashes. Only generated/runtime output differs (compiler stamp v0.83.0, bundled copilot engine 1.0.71->1.0.73, action pins, image digests). Refs github/plan-track-agentic-toolkit#516 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
| GH_AW_GITHUB_RUN_ID: ${{ github.run_id }} | ||
| GH_AW_GITHUB_WORKSPACE: ${{ github.workspace }} | ||
| GH_AW_MCP_CLI_SERVERS_LIST: '- `safeoutputs` — run `safeoutputs --help` to see available tools' | ||
| GH_AW_MCP_CLI_SERVERS_LIST: "- `github` — run `github --help` to see available tools\n- `safeoutputs` — run `safeoutputs --help` to see available tools" |
Enable native issue intents (rationale/confidence) on every configured safe-output that supports issue-intent in gh-aw v0.83.0, across the 11 scoped workflows. Adds no new tools and changes no other behavior. Enabled on: - add-labels: cross-repo-issue-analysis, handle-bug, handle-documentation, handle-enhancement, handle-question, issue-triage - close-issue: issue-triage create-issue is not included: the v0.83.0 compiler does not emit issue_intent for create-issue (its handler builder omits the field), so the key would be inert. Unsupported safe-outputs (add-comment, update-issue) are left untouched. Recompiled with gh-aw v0.83.0; non-affected lock files are byte-identical. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
Contributor
There was a problem hiding this comment.
Review details
Comments suppressed due to low confidence (1)
.github/workflows/issue-triage.md:33
- This additionally enables issue intents for closing issues, which is a source-level behavior change omitted by the PR description. Either remove it for the stated compiler-only refresh or explicitly document and validate the new close-issue intent behavior and activation requirements.
issue-intent: true
- Files reviewed: 21/21 changed files
- Comments generated: 6
- Review effort level: Medium
| allowed: [bug, enhancement, question, documentation] | ||
| max: 1 | ||
| target: "*" | ||
| issue-intent: true |
| allowed: [documentation] | ||
| max: 1 | ||
| target: "*" | ||
| issue-intent: true |
| allowed: [enhancement] | ||
| max: 1 | ||
| target: "*" | ||
| issue-intent: true |
| allowed: [question] | ||
| max: 1 | ||
| target: "*" | ||
| issue-intent: true |
| allowed: [runtime, sdk-fix-only, needs-investigation] | ||
| max: 3 | ||
| target: triggering | ||
| issue-intent: true |
…kflow Complete the issue-intent audit against the v0.83.0 schema: every already-configured safe-output whose schema supports issue-intent now declares `issue-intent: true`. This adds it to `create-issue` in cross-repo-issue-analysis, the one remaining schema-supported tool. No tools added; no repo variables changed. Only the source frontmatter and its lock's frontmatter_hash change (the create-issue handler does not emit issue_intent at runtime, so the compiled safe-outputs config and body are unchanged). Full schema-supported enablement across the PR github#1880 scope: - add-labels: cross-repo-issue-analysis, handle-bug, handle-documentation, handle-enhancement, handle-question, issue-triage - close-issue: issue-triage - create-issue: cross-repo-issue-analysis Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
Setup PR github#1880 ("Enable built-in issue intent safe outputs on issue-triage") meaningfully scoped issue intent to the issue-triage workflow. Revert the issue-intent frontmatter that had been added to the other five workflows (cross-repo-issue-analysis, handle-bug, handle-documentation, handle-enhancement, handle-question) and recompile at gh-aw v0.83.0. Net effect vs main: - issue-triage.md: issue-intent enabled on add-labels + close-issue. - All other workflows: v0.82.10 -> v0.83.0 generated version bump only. - Shared generated files (actions-lock.json, agentics-maintenance.yml, copilot-setup-steps.yml, verify-compiled.yml): v0.83.0. Compiled with gh-aw v0.83.0; idempotent. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
Contributor
There was a problem hiding this comment.
Review details
Comments suppressed due to low confidence (1)
.github/workflows/release-changelog.lock.yml:331
- The claim that other workflows have “no … behavioral changes” is inaccurate: this recompile now exposes the
githubMCP CLI to the agent, and the same generated locks enablefields_param, add invocation-cap handling, and upgrade the engine/runtime components. Unchanged source hashes only show that source workflow definitions were preserved. Please describe this as no source configuration change and summarize the runtime behavior changes introduced by the upgrade.
GH_AW_MCP_CLI_SERVERS_LIST: "- `github` — run `github --help` to see available tools\n- `safeoutputs` — run `safeoutputs --help` to see available tools"
- Files reviewed: 16/16 changed files
- Comments generated: 0 new
- Review effort level: Medium
Reduce the PR to the minimal net diff: only the issue-triage workflow (the workflow meaningfully scoped by setup PR github#1880) is refreshed to gh-aw v0.83.0 and gains issue-intent. All other workflows are left untouched at their base v0.82.10 compiled state. Compiled issue-triage alone with `gh aw compile issue-triage` (v0.83.0), which regenerates only issue-triage.lock.yml and the shared actions-lock.json setup pin. The other 10 lock files, agentics- maintenance.yml, and copilot-setup-steps.yml are reverted to base. verify-compiled.yml (hand-authored CI) is pinned to v0.83.0 and scoped to `gh aw compile issue-triage` so the mixed-version repo verifies cleanly without rewriting the untouched locks. Net diff vs base: - issue-triage.md: issue-intent on add-labels + close-issue - issue-triage.lock.yml: v0.83.0 recompile - .github/aw/actions-lock.json: gh-aw setup pinned v0.83.0 - verify-compiled.yml: CI pinned v0.83.0, compiles issue-triage only Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
Retarget the scoped refresh from v0.83.0 to the latest stable gh-aw release v0.83.1. Only the issue-triage workflow is refreshed; all other workflows remain untouched at their base v0.82.10 compiled state. Net diff vs base (4 files): - issue-triage.md: issue-intent on add-labels + close-issue - issue-triage.lock.yml: recompiled with gh-aw v0.83.1 - .github/aw/actions-lock.json: gh-aw setup pinned v0.83.1 - verify-compiled.yml: CI pinned v0.83.1, compiles issue-triage only Compiled with `gh aw compile issue-triage` (v0.83.1); idempotent. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
| version: v0.83.0 | ||
| - name: Recompile workflows | ||
| run: gh aw compile | ||
| run: gh aw compile issue-triage |
Restore the standard full-repository refresh: all 11 workflows are recompiled with the latest stable gh-aw release v0.83.1 via the normal `gh aw compile`, and CI (verify-compiled.yml) is pinned to v0.83.1 with the full compile restored. Source changes are limited to a single workflow: issue-triage.md gains issue-intent on add-labels + close-issue. The other 10 workflow source .md files are byte-identical to base; their lock files change only by the v0.82.10 -> v0.83.1 generated version bump. Source vs generated: - Source (.md): issue-triage.md only (issue-intent) - Generated locks: all 11 *.lock.yml recompiled at v0.83.1 (issue_intent config present only in issue-triage.lock.yml) - Generated shared: .github/aw/actions-lock.json, agentics-maintenance.yml - CI config: verify-compiled.yml pinned v0.83.1, full `gh aw compile` Compiled with gh-aw v0.83.1; idempotent. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
Contributor
There was a problem hiding this comment.
Review details
Comments suppressed due to low confidence (1)
.github/workflows/verify-compiled.yml:24
- This removes stale-lock verification for every workflow except
issue-triage, even though the job still runs for changes to any workflow source or lock file. For example, a PR can changehandle-question.mdwithout recompiling its lock; this command leaves the working tree clean and the job reports that all lock files are current. Please preserve coverage for the ten v0.82.10 workflows (for example, verify them with that pinned compiler and compare their generated files separately), then verifyissue-triagewith v0.83.1, or upgrade all locks together.
run: gh aw compile
- Files reviewed: 15/15 changed files
- Comments generated: 0 new
- Review effort level: Medium
Restore the latest-stable install behavior in verify-compiled.yml instead of pinning the CLI version. The setup-cli action's `version: latest` resolves to the latest non-prerelease gh-aw release (v0.83.1 today), so CI reproduces the committed v0.83.1 locks via the standard full `gh aw compile` without hard-pinning committed config to a specific version. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
| uses: github/gh-aw-actions/setup-cli@8bdba8075360648fe6802302a5b4e016361dc6ac # v0.83.1 | ||
| with: | ||
| version: v0.82.10 | ||
| version: v0.83.1 |
Clarify (comment-only) that verify-compiled installs the latest stable gh-aw release dynamically via `version: latest` (no version pin) and runs the full-repository `gh aw compile` so the diff check covers all 11 workflows. No behavior change; the action-code SHA remains base-pinned for supply-chain safety while the CLI version floats to latest stable. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b18ddbb6-b994-4a4b-9096-a16d52309df7
Contributor
There was a problem hiding this comment.
Review details
Comments suppressed due to low confidence (1)
.github/workflows/verify-compiled.yml:24
- The generated lock files record compiler version
v0.83.1, so resolvinglatestmakes this check non-reproducible: as soon as the next stable gh-aw release appears, every PR touching a workflow will regenerate at least the metadata and fail until the repository is upgraded again. Pin the verifier to the same CLI/action revision as the committed locks; use maintenance automation to perform future upgrades deliberately.
uses: github/gh-aw-actions/setup-cli@05205436a78512d71a2d842e46586ed05f4fa058 # v0.82.10
with:
version: latest
- Files reviewed: 15/15 changed files
- Comments generated: 0 new
- Review effort level: Medium
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
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.
Summary
Refreshes all agentic workflows in the repository to the latest stable gh-aw release v0.83.1, and enables native issue intents on the issue-triage workflow (the workflow meaningfully scoped by setup PR #1880, "Enable built-in issue intent safe outputs on issue-triage").
Source vs generated changes
Source change — one workflow only:
.github/workflows/issue-triage.mdissue-intent: trueadded toadd-labels+close-issue(the only configured safe-outputs whose v0.83.1 schema supports it)The other 10 workflow source
.mdfiles are byte-identical to base — no prompt, trigger, permission, tool, safe-output, network, or engine changes.Generated / config (produced by
gh aw compileat v0.83.1):*.lock.ymlrecompiled at v0.83.1 (v0.82.10 → v0.83.1 version bump).issue_intentconfig appears only inissue-triage.lock.yml..github/aw/actions-lock.json— gh-aw setup action pinned@v0.83.1..github/workflows/agentics-maintenance.yml— regenerated at v0.83.1..github/workflows/verify-compiled.yml— CI installs latest-stable gh-aw (version: latest, currently v0.83.1) and runs the standard fullgh aw compile; not hard-pinned to a specific version.No safe-output tools were added and no repository variables were modified.
Validation
gh aw compileat v0.83.1: 11 workflows, 0 errors (2 pre-existing/tmppath warnings on the two Java workflows, unrelated to this change).gh aw compileproduced byte-identical output.verifyjob installs latest-stable gh-aw and runs fullgh aw compile, verifying all lock files are up to date.Refs github/plan-track-agentic-toolkit#516