Skip to content

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

Closed as not planned

Description

@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

Activity

  1. strawgate commented on Feb 21, 2026

    @strawgate
    Contributor

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

  2. github-actions commented on Feb 21, 2026

    @github-actions
    ContributorAuthor

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

    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.

  3. github-actions commented on Feb 22, 2026

    @github-actions
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions