[gh-aw-upgrade] gh-aw upgrade available: v0.48.1 → v0.48.2

[github-actions]

A new version of gh-aw is available. We are currently on v0.48.1, latest is v0.48.2.

Upgrade Assessment

Urgency: Recommended

Relevant Changes

v0.48.2

Breaking Changes

• None identified for our current workflow frontmatter usage.

New Features Worth Adopting

• update-issue supports title-prefix: available for future workflows that use update-issue safe output.
• Auto-inject create-issue safe output: improves safety for new workflows that forget explicit non-builtin safe outputs.

Bug Fixes

• Activation/pre-activation output correctness: release notes call out fixes for invalid needs.pre_activation.outputs.* references and undefined matched_command output.
  • We currently have the exact mismatch in compiled workflows, e.g. .github/workflows/gh-aw-release-update.lock.yml#L403 references needs.pre_activation.outputs.matched_command, but .github/workflows/gh-aw-release-update.lock.yml#L1437-L1439 only defines activated in pre_activation.outputs.
  • This mismatch appears broadly across compiled lock workflows (40 gh-aw-*.lock.yml files with needs.pre_activation.outputs.matched_command references but no matched_command output declared in pre_activation.outputs).
• Safe-output schema validation improvements: better diagnostics for malformed safe-output config, useful for our many safe-outputs workflow definitions.

Security

• No explicit security patch requiring an immediate workflow config change was identified in v0.48.2 notes.

Upgrade Steps

• Update GH_AW_VERSION in Makefile from v0.48.1 to v0.48.2
• Run make compile to regenerate *.lock.yml with compiler fixes (especially pre-activation output wiring)
• Run make lint-workflows and verify 0 errors
• Spot-check representative lock workflows (e.g. gh-aw-release-update.lock.yml) to confirm pre_activation.outputs includes matched_command when referenced

Generated by Upgrade Check

• expires on Feb 28, 2026, 6:41 PM UTC

[strawgate]

/ai does this address #191 and we can undo that change when we upgrade? can you verify and if so make a pr

[github-actions]

Verified: v0.48.2 does address the #191 workaround path, and I opened a PR with the upgrade plus the workaround removal changes.

• Upgraded GH_AW_VERSION in Makefile:4 to v0.48.2.
• Confirmed upstream fix is in v0.48.2 release notes: update-pull-request now honors footer: false (fix for update-pull-request should honor footer: false github/gh-aw#17522, with related footer work from create_pull_request does not apply messages.footer template github/gh-aw#17074 now closed).
• Prepared the workaround removal changes at:
  • github/workflows/gh-aw-update-pr-body.md:87 (removed global safe-outputs.messages.footer: "" override)
  • github/workflows/gh-aw-fragments/safe-output-update-pr.md:5 (set footer: false under update-pull-request)
• Validation: make lint-workflows passed.

Note: workflow-file edits are staged under github/workflows/ for maintainer relocation into .github/workflows/.

---

What is this? | From workflow: Mention in Issue

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #371

View newer issue

---

This action was performed automatically by the Internal: Upgrade Check workflow.