awf-release-integrator
Upgrade gh-aw firewall and MCP gateway releases, refresh trusted pins, and identify follow-up spec tasks.
Try your first task
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: awf-release-integratordescription: Upgrade gh-aw firewall and MCP gateway releases, refresh trusted pins, and identify follow-up spec tasks.AWF Release Integrator
Use this skill when updating github/gh-aw to newer github/gh-aw-firewall or github/gh-aw-mcpg releases.
Goal
Land the version bump cleanly, rebuild the generated artifacts, and review upstream release/spec changes for any follow-up work that should accompany the bump.
Required sources
Consult these sources before editing anything:
- The latest
github/gh-aw-firewallandgithub/gh-aw-mcpgrelease metadata and bodies. - The current gh-aw version pins in
pkg/constants/version_constants.go. - The canonical AWF config sources spec in
specs/awf-config-sources-spec.md. - The embedded AWF schema in
pkg/workflow/schemas/awf-config.schema.json. - AWF config integration code in:
pkg/workflow/awf_config.gopkg/workflow/awf_config_build.gopkg/workflow/awf_config_schema.gopkg/workflow/awf_config_policy.gopkg/workflow/awf_helpers.go- related AWF tests under
pkg/workflow/
For upstream spec review, compare these files from the target github/gh-aw-firewall release or tag:
docs/awf-config-spec.mddocs/awf-config.schema.jsonsrc/awf-config-schema.json- any release assets such as
awf-config.schema.json
Update procedure
- Read
pkg/constants/version_constants.goand record:DefaultFirewallVersion- every
AWF*MinVersionconstant DefaultMCPGatewayVersion
- Look up the latest release metadata for both
github/gh-aw-firewallandgithub/gh-aw-mcpg; assess each default independently. - If neither release is newer than its default, report that no version bump is needed and only continue with spec/release-note review if explicitly requested.
- For a newer AWF release:
- bump
DefaultFirewallVersion - update any
AWF*MinVersionconstants that must move because the new release introduces or changes gated flags/features - add a reviewed
checksums.txtdigest toactions/setup/sh/release_integrity.shusingscripts/update-release-pins.sh. Obtain the digest from an independently trusted source such as the GitHub release API asset metadata, and verify it matches the downloaded manifest; never trust a checksum downloaded only alongside the release. - add the exact digest to the pin assertions in
actions/setup/sh/release_integrity_test.shand confirmpkg/workflow/firewall_version_pinning_test.goaccepts the new compiler default.
- bump
- For a newer MCP gateway release:
- bump
DefaultMCPGatewayVersionand update its direct test expectation - add the new image and verified digest to
.github/aw/actions-lock.json; runmake buildto synchronizepkg/actionpins/data/action_pins.jsonandpkg/workflow/data/action_pins.json
- bump
- Review release notes for:
- new flags
- removed or deprecated flags
- schema/config additions
- security fixes
- behavioral changes that could require new tests, docs, or ADR/spec updates
- Review the upstream AWF specification and schema changes against:
pkg/workflow/schemas/awf-config.schema.jsonspecs/awf-config-sources-spec.md- local AWF config generation and validation code
- Update any directly related gh-aw files needed for a complete integration, such as:
- embedded schema copies
- version-gated helpers/tests
- specs or ADRs documenting newly surfaced AWF behavior
- Run
make build, then runmake recompiletwice to refresh image SHA pins and generated workflow locks. - Add or update a patch changeset when the bump changes shipped behavior.
Required validation
After the update procedure, run focused validation for any touched Go code or schema logic, especially AWF-related tests, plus the release-integrity tests when adding an AWF checksum pin.
Expected output
Summarize:
- current gh-aw AWF version → target release
- current MCP gateway version → target release
- updated constants, reviewed checksum pin, and image digests
- release-note highlights
- specification/schema differences reviewed
- additional recommended follow-up updates that are not yet implemented
Review heuristics
When deciding whether more than a version bump is needed, specifically check for:
- new AWF schema properties not represented in gh-aw
- new CLI flags that need
AWF*MinVersiongates - config fields present in schema but absent from gh-aw generation/validation
- drift that should update
specs/awf-config-sources-spec.md - tests whose expected pinned AWF version or schema URLs need refresh