awf-release-integrator

Solid

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

AI & Automation 4,819 stars 466 forks Updated today MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# AWF Release Integrator Use this skill when updating `github/gh-aw` to a newer `github/gh-aw-firewall` release. ## 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: 1. The latest `github/gh-aw-firewall` release metadata and body. 2. The current gh-aw version pins in `pkg/constants/version_constants.go`. 3. The canonical AWF config sources spec in `specs/awf-config-sources-spec.md`. 4. The embedded AWF schema in `pkg/workflow/schemas/awf-config.schema.json`. 5. AWF config integration code in: - `pkg/workflow/awf_config.go` - `pkg/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.md` - `docs/awf-config.schema.json` - `src/awf-config-schema.json` - any release assets such as `awf-config.schema.json` ## Update procedure 1. Read `pkg/constants/version_constants.go` and record: - `DefaultFirewallVersion` - every `AWF*MinVersion` constant 2. Look up the latest `github/gh-aw-firewall` release. 3. If the latest release tag matches `DefaultFirewallVersion`, report that no version bump is needed and only continue with spec/release-note review if explicitly requested. 4. If a newer release exists, update the gh-aw pins: - bump `DefaultFirew...

Details

Author
github
Repository
github/gh-aw
Created
11 months ago
Last Updated
today
Language
Go
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

dependency-upgrade

Bring a repo's dependencies up to the latest versions across JavaScript (npm/pnpm/yarn), Ruby (bundler), Python (uv/poetry/pip), and GitHub Actions — reading changelogs/migration guides for major bumps, applying the needed code changes, and landing each step as its own verified commit. Use when the user wants to "update my packages", "upgrade dependencies", "bump deps to latest", "check for outdated packages", or do this across all their repos (fleet mode). Gates every commit on a green test suite; defers any major it can't get green to a written report. Pairs with the github-actions skill (Actions pins) and respects dev-env-setup's 4-day dependency cooldown.

0 Updated 2 days ago
mickzijdel
AI & Automation Solid

dependency-upgrade

Use when a dependency is outdated or has a known vulnerability and you need to upgrade it safely with the right changelog and migration notes.

1 Updated 5 days ago
NSBen
AI & Automation Listed

release-workflow

End-to-end release process: semver level decisions from Conventional Commits, changelog generation, annotated git tags, GitHub Releases via gh CLI, version bump locations, hotfix branching, and CI automation shape. Use this skill whenever you are cutting a release, bumping a version, generating or updating a changelog, creating a git tag or GitHub Release, deciding which semver level to apply (major/minor/patch), handling a hotfix release, or working through a release checklist. If the user asks "what version should this be?", "how do I tag this?", "create a release", or "we need a hotfix" — load this skill first.

0 Updated today
sardonyx0827