Skip to content

Add scheduled workflow to upgrade gh-aw agentic workflows#38829

Open
jeremymeng wants to merge 2 commits into
mainfrom
jeremymeng/upgrade-aw-workflow
Open

Add scheduled workflow to upgrade gh-aw agentic workflows#38829
jeremymeng wants to merge 2 commits into
mainfrom
jeremymeng/upgrade-aw-workflow

Conversation

@jeremymeng
Copy link
Copy Markdown
Member

Keeping gh-aw and the compiled .lock.yml files current is currently a manual chore that has to be remembered and repeated whenever upstream cuts a release. This adds a scheduled agentic workflow that does the upgrade end-to-end and proposes the result as a single PR for review.

Approach

A new workflow at .github/workflows/upgrade-agentic-workflows.md runs weekly (and on workflow_dispatch) and does the following:

  1. Reads the currently pinned gh-aw version from .github/workflows/copilot-setup-steps.yml, queries github/gh-aw for the latest release, and exits early if we are already current.
  2. Runs gh aw upgrade from the repo root, applies the reported codemods, and makes surgical edits to individual workflow .md files for any deprecations / breaking changes it cannot auto-fix.
  3. Runs gh aw compile to regenerate every .lock.yml, fixing source files and re-compiling until the command exits cleanly.
  4. Bumps the pinned version everywhere it is referenced:
    • uses: github/gh-aw-actions/setup-cli@<sha> # v<version> and with.version in copilot-setup-steps.yml (both the SHA and tag).
    • Every https://github.com/github/gh-aw/blob/v<old>/... URL in .github/agents/agentic-workflows.agent.md.
  5. Sanity-checks the diff is scoped to the expected files, then opens a single PR via safe-outputs.create-pull-request (draft if any upgrade or compile issue could not be resolved automatically, otherwise a regular PR).

Notes

  • The workflow uses safe-outputs.create-pull-request exclusively; it does not push commits or open PRs through the gh CLI directly.
  • Schedule uses the fuzzy weekly on monday cron form to distribute load.
  • Compiled locally with gh aw compile: 0 errors, 0 warnings. Both the source .md and generated .lock.yml are included.

Adds .github/workflows/upgrade-agentic-workflows.md, a weekly workflow that runs `gh aw upgrade`, resolves any reported issues, recompiles all workflows, and bumps the pinned gh-aw version in .github/agents/agentic-workflows.agent.md and .github/workflows/copilot-setup-steps.yml. Changes ship via a single safe-output pull request.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 4, 2026 22:07
@jeremymeng jeremymeng requested a review from a team as a code owner June 4, 2026 22:07
@jeremymeng jeremymeng requested a review from a team June 4, 2026 22:08
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new scheduled Agentic Workflows job intended to automatically upgrade gh-aw, recompile all workflow .lock.yml files, update pinned references, and open a single PR via safe-outputs.create-pull-request.

Changes:

  • Added .github/workflows/upgrade-agentic-workflows.md defining the weekly/dispatchable upgrade procedure and constraints.
  • Added the compiled workflow .github/workflows/upgrade-agentic-workflows.lock.yml generated from the markdown source.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
.github/workflows/upgrade-agentic-workflows.md New agentic workflow source defining the upgrade/compile/version-bump PR process.
.github/workflows/upgrade-agentic-workflows.lock.yml Generated compiled workflow to be executed by GitHub Actions.

Comment thread .github/workflows/upgrade-agentic-workflows.lock.yml Outdated
Comment thread .github/workflows/upgrade-agentic-workflows.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants