Update gh-aw-upgrade prompt #92

Activity

1. github-actions commented on Feb 17, 2026

   

   github-actionsBot

   on Feb 17, 2026 – with GitHub Actions

   Contributor

   More actions

   Update the gh-aw-upgrade-check prompt to require a concise Recommendation plus explicit Upgrade Risks and Features to Adopt sections, then recompile so the lock file reflects the new issue template.

   Recommendation

   Revise .github/workflows/gh-aw-upgrade-check.md so the generated issue body starts with a clear Recommendation (upgrade now/delay/skip) and includes focused sections for Upgrade Risks and Features to Adopt that are tied to our current workflow usage, then run make compile to refresh .github/workflows/gh-aw-upgrade-check.lock.yml.

   Findings

   • The upgrade-check prompt is defined in .github/workflows/gh-aw-upgrade-check.md and its Issue Format currently centers on an “Urgency” label and a “Relevant Changes” breakdown, but does not require a recommendation or a “problems after upgrading” section.
   • Existing upgrade issues (e.g., [gh-aw-upgrade] gh-aw upgrade available: v0.45.1 → v0.45.4 #91, [gh-aw-upgrade] gh-aw upgrade available: v0.45.0 → v0.45.1 #69) follow this template and already include “Urgency” and “Relevant Changes,” which is close but not aligned with the requested structure.

   `.github/workflows/gh-aw-upgrade-check.md` (lines 65-100) currently specifies:
   
   ## Upgrade Assessment
   
   **Urgency:** [Critical / Recommended / Informational]
   
   ## Relevant Changes
   
   ### [version tag]
   
   #### Breaking Changes (if any)
   - **[change]**: [impact on our workflows and what needs updating]
   
   #### New Features Worth Adopting
   - **[feature]**: [what it does and which of our workflows would benefit]
   
   #### Bug Fixes
   - **[fix]**: [what was broken and whether it affects us]
   
   #### Security
   - **[patch]**: [what was addressed]
   
   ## Upgrade Steps
   
   - [ ] Update `GH_AW_VERSION` in `Makefile` from `[current]` to `[latest]`
   - [ ] [Any workflow file changes needed for breaking changes]
   - [ ] Run `make compile` and verify 0 errors, 0 warnings
   - [ ] [Any other specific steps]

   Verification

   Not run (prompt-only change; no runtime behavior to validate).

   Detailed Action Plan

   1. In .github/workflows/gh-aw-upgrade-check.md:
      • Update What to Look For (lines ~42-49) to explicitly require: (a) a concrete recommendation, (b) upgrade risks rooted in how we use gh-aw, and (c) features to adopt that map to current workflow usage.
      • Update How to Analyze (lines ~53-57) to prioritize recommendation + risk + feature relevance over generic release notes.
      • Replace the Issue Format block (lines ~65-100) with a concise structure such as:
        • Recommendation (upgrade now/delay/skip + brief rationale)
        • Upgrade Risks (specific breakages or behavior changes tied to our workflows)
        • Features to Adopt (feature + workflow(s) it benefits)
        • Relevant Changes (only the subset that substantiates the above)
        • Upgrade Steps (keep existing checklist)
   2. Run make compile to regenerate .github/workflows/gh-aw-upgrade-check.lock.yml and confirm the new issue template is compiled into the lock file.

   Related Items

   Type	Link	Relevance
   Issue	#91	Latest upgrade issue generated by current prompt
   Issue	#69	Prior upgrade issue showing current template structure
   PR	#72	Recent gh-aw version bump and compile steps
   File	.github/workflows/gh-aw-upgrade-check.md	Prompt source to update

   ---

   What is this? | From workflow: Issue Triage

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #92
2. strawgate commented on Feb 18, 2026

   

   strawgate

   on Feb 18, 2026

   ContributorAuthor

   More actions

   /AI make a pr

   👀React with 👀1Reacted by github-actions
3. strawgate commented on Feb 18, 2026

   

   strawgate

   on Feb 18, 2026

   ContributorAuthor

   More actions

   /ai make a pr

   👀React with 👀1Reacted by github-actions
4. github-actions commented on Feb 18, 2026

   

   github-actionsBot

   on Feb 18, 2026 – with GitHub Actions

   Contributor

   More actions

   PR created to update the gh-aw upgrade-check prompt with explicit Recommendation, Upgrade Risks, and Features to Adopt sections tied to current workflow usage. Copies live under github/workflows/ per workflow-editing guardrails; please relocate them into .github/workflows/ and run make compile to regenerate the canonical lock file.

   github/workflows/gh-aw-upgrade-check.md:L60-L116
   60. ### What to Look For
   61.
   62. Compare the release notes and changelog entries against our workflow configurations. Focus on:
   63.
   64. 1. **Recommendation** — upgrade now/delay/skip based on impact to our current workflows
   65. 2. **Upgrade risks** — breaking changes or behavior shifts that would cause problems in our existing workflows
   66. 3. **Features to adopt** — new capabilities that map directly to how we use gh-aw today
   67. 4. **Supporting evidence** — only the specific release notes that justify the recommendation, risks, and features
   ...
   91. > ## Recommendation
   92. >
   93. > **[Upgrade now / Delay / Skip]** — [brief rationale tied to our workflows]
   94. >
   95. > ## Upgrade Risks
   96. >
   97. > - **[risk]**: [what breaks or changes, and which workflow(s) it impacts]
   98. >
   99. > ## Features to Adopt
   100. >
   101. > - **[feature]**: [what it enables and which workflow(s) benefit]
   102. >
   103. > ## Relevant Changes
   104. >
   105. > ### [version tag]
   106. >
   107. > - **[change]**: [only the items that support the recommendation, risks, or features]
   

   Tests not run (prompt-only change; make compile not run in this environment).

   ---

   What is this? | From workflow: Issue Assistant

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #92
5. strawgate

   closed this as completedin #106on Feb 18, 2026