chore: upgrade community workflows to gh-aw v0.88.7 - #4615
Merged
KSchlobohm merged 1 commit intoSep 17, 2026
Merged
Conversation
Regenerate the three community submission locks with Copilot CLI 1.0.80 and the compiler defaults. Preserve submission instructions and file allowlists, and cover runtime compatibility and output guards. Assisted-by: GitHub Copilot (model: GPT-6 Astra, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
馃數 Needs a closer look
The large security-sensitive generated workflow changes and untested rejection paths warrant final human review.
Review effort: Balanced
Findings: None
What changed in this PR
Upgrades all community submission workflow locks to gh-aw v0.88.7 and Copilot CLI 1.0.80 while preserving security and output constraints.
Changes:
- Regenerates three workflow locks with updated immutable dependencies and runtime defaults.
- Adds compatibility tests for permissions, activation, draft PR limits, and fail-closed threat detection.
| File | Description |
|---|---|
.github/鈥媤orkflows/鈥媋dd-community-extension.lock.yml |
Upgrades extension automation runtime. |
.github/鈥媤orkflows/鈥媋dd-community-preset.lock.yml |
Upgrades preset automation runtime. |
.github/鈥媤orkflows/鈥媋dd-community-bundle.lock.yml |
Upgrades bundle automation runtime. |
tests/鈥媡est_github_workflows.py |
Verifies upgraded workflow contracts. |
馃挕 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Upgrade the three community submission workflows鈥攅xtension, preset, and bundle鈥攆rom gh-aw v0.79.8 / Copilot CLI 1.0.60 to gh-aw v0.88.7 / Copilot CLI 1.0.80, matching the baseline established by #4604.
autofallback model. Existing repository model variables still take precedence.Submission instructions are unchanged. Each workflow retains its two-file allowlist and draft-only PR configuration. The narrower Copilot-specific protected-file defaults do not expand those allowlists.
The changeset contains only three generated locks and
tests/test_github_workflows.py. No catalog changes, documentation changes, shared action-pin edits, or submission-logic fixes are included.Testing
uv run specify --helpLocal validation:
python -m pytest tests/test_github_workflows.py -q: 27 passed, 7 existing Bash-dependent cases skipped on Windows.--strict --validate --no-check-update: all three workflows compiled without warnings.git diff --checkpassed.Controlled fork runs used the merged upgrade revision
35129c6a49a2508c95676c3287ae11267924be23. Each submission label automatically started its intended workflow, which appliedvalidation-passedand created a draft PR against the fork'smain.The generated PRs stayed within their allowed files. Extension and preset updates matched the expected catalog data.
Limitations: The bundle PR updated its version and download URL but retained the old Spec Kit requirement instead of the submitted
>=0.14.0,<2.0.0. This is recorded as a separate content-correctness issue; its cause has not been isolated to the compiler upgrade. Nonblocking cache-permission warnings and literal\nseparators in some generated commit messages were also observed. Rejection-path scenarios were not run.This evidence establishes successful label-to-PR execution, not complete decision-flow or content correctness.
AI Disclosure
GitHub Copilot (GPT-6 Astra) prepared the generated locks, compatibility tests, local validation, controlled fork-test fixtures, and this description on behalf of @KSchlobohm. The human contributor directed scope and approved the compiler defaults and fork test runs. The agent-authored commit includes attribution.