Regenerate pr-docs workflow with gh-aw v0.67.2#15943
Merged
IEvangelist merged 2 commits intomicrosoft:mainfrom Apr 7, 2026
Merged
Regenerate pr-docs workflow with gh-aw v0.67.2#15943IEvangelist merged 2 commits intomicrosoft:mainfrom
IEvangelist merged 2 commits intomicrosoft:mainfrom
Conversation
Regenerate the lock file from the current pr-docs-check markdown source so activation no longer fails the stale lock-file hash check. Preserve the existing same-job checkout-token workaround in the generated workflow so the agent can still check out aspire.dev. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 15943Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 15943" |
Recompile the pr-docs-check workflow with the official gh-aw v0.67.2 release binary so the generated workflow records the correct compiler version and keeps the cross-repo checkout token in the agent job. Include the corresponding gh-aw-actions setup pin in .github/aw/actions-lock.json and preserve the least-privilege permission trim in the generated lock file. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
IEvangelist
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
Restores the reliability of the pr-docs-check agentic workflow by regenerating its compiled lock file and updating the pinned gh-aw setup action to match v0.67.2, aligning the generated workflow with the current markdown source and compiler behavior.
Changes:
- Recompiled
pr-docs-check.lock.ymlto match.github/workflows/pr-docs-check.mdand recordgh-aw v0.67.2metadata/pins. - Updated the generated workflow content to the
v0.67.2output shape (including the safe-outputs tooling generation and checkout/token step ordering in the agent job). - Added the corresponding
github/gh-aw-actions/setup@v0.67.2entry to.github/aw/actions-lock.json.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/pr-docs-check.lock.yml | Regenerated lock workflow (metadata hash, setup action pin, and generated step structure) using gh-aw v0.67.2. |
| .github/aw/actions-lock.json | Adds the setup@v0.67.2 pin entry used by the regenerated workflow. |
radical
approved these changes
Apr 7, 2026
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
Follow-up to the still-broken
pr-docs-checkworkflow after #15929.Root cause
Run https://github.com/microsoft/aspire/actions/runs/24102304492 fails in
activationduringCheck workflow lock filebecause the checked-in lock file drifted from.github/workflows/pr-docs-check.md.What this changes
pr-docs-check.lock.ymlfrom the current markdown source so the activation hash check passes again.gh-aw v0.67.2release binary, so the generated workflow keeps the cross-repo checkout token in theagentjob instead of the stripped activation output pattern..github/aw/actions-lock.jsonwith the correspondinggithub/gh-aw-actions/setup@v0.67.2pin.Notes
gh extension upgrade gh-awcurrently follows the stable GitHub release API and downgrades back tov0.67.1, becausev0.67.2is published as a prerelease.v0.67.2Windows release binary directly so the checked-in workflow now recordscompiler_version: v0.67.2.