awf-release-integrator

Upgrade gh-aw to the latest gh-aw-firewall release and identify follow-up spec tasks.

5.1k|530|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill awf-release-integrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: awf-release-integrator
Source: https://github.com/github/gh-aw/tree/main/.github/skills/awf-release-integrator
Command: npx skills add https://github.com/github/gh-aw --skill awf-release-integrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping the gh-aw repository in sync with upstream gh-aw-firewall (AWF) releases requires manually tracking version pins, release notes, schema changes, and spec drift across many files, which is error-prone and easy to miss follow-up work.

Core Features & Use Cases

  • Version Bump Automation: Updates DefaultFirewallVersion and AWF*MinVersion constants in pkg/constants/version_constants.go when a newer gh-aw-firewall release exists.
  • Spec and Schema Drift Review: Compares upstream AWF spec and schema files against the embedded awf-config.schema.json and specs/awf-config-sources-spec.md to surface gaps.
  • Validated Rebuild Flow: Runs the required make build and double make recompile sequence to refresh generated artifacts and image SHA pins.
  • Use Case: When gh-aw-firewall publishes a new release with new CLI flags or schema properties, use this Skill to bump the pins, gate new flags behind version constants, update tests and specs, and produce a summary of remaining follow-up work.

Quick Start

Upgrade gh-aw to the latest gh-aw-firewall release and report any spec or schema follow-up tasks.

Frequently Asked Questions about awf-release-integrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade gh-aw to a new gh-aw-firewall release?

Check the latest gh-aw-firewall release, then bump DefaultFirewallVersion and any affected AWF*MinVersion constants in pkg/constants/version_constants.go. Afterward run make build followed by make recompile twice to refresh generated artifacts and image SHA pins.

How do I detect AWF schema drift between gh-aw and gh-aw-firewall?

Compare the upstream docs/awf-config-spec.md and awf-config schema files from the target release against pkg/workflow/schemas/awf-config.schema.json and specs/awf-config-sources-spec.md. Look for new properties, removed flags, or config fields missing from gh-aw generation and validation code.

Why is make recompile run twice after an AWF version bump?

The first make recompile resolves new image SHA pins during the rebuild, and the second pass refreshes the generated artifacts with those resolved pins. Skipping the second run can leave stale pins in compiled workflows.

When is no version bump needed for gh-aw-firewall integration?

If the latest gh-aw-firewall release tag already matches DefaultFirewallVersion in version_constants.go, no bump is required. In that case only spec and release-note review continues if explicitly requested.

What follow-up changes can an AWF release require beyond version pins?

New releases can introduce CLI flags needing AWF*MinVersion gates, schema properties absent from gh-aw validation, deprecated flags, and security fixes. These may require updates to embedded schemas, tests, specs, ADRs, and a patch changeset.