⚙️ [Maintenance]: Bring workflows into compliance with the GitHub Actions standard#31
Merged
Marius Storhaug (MariusStorhaug) merged 1 commit intoJul 9, 2026
Conversation
Pin runner images (ubuntu-24.04, windows-2025, macos-15) and set cancel-in-progress: false on the release workflow so publishing runs queue instead of aborting mid-write. Fixes #29
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 9, 2026 11:10
View session
There was a problem hiding this comment.
Pull request overview
Aligns this repository’s inline GitHub Actions workflows with the organization’s GitHub Actions coding standard by pinning runner images to explicit versions and ensuring publish/release workflows queue rather than cancel in-progress runs.
Changes:
- Pinned
runs-onacross workflows (including the test matrix) to explicit runner images instead of*-latest. - Updated the release workflow concurrency behavior to
cancel-in-progress: falseso publishing runs queue safely. - Kept
cancel-in-progress: truefor non-publishing workflows (test/lint) to avoid wasting CI on superseded runs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/Release.yml | Pins runner to ubuntu-24.04 and queues release runs by setting cancel-in-progress: false. |
| .github/workflows/Linter.yml | Pins linter runner to ubuntu-24.04 while retaining cancellable concurrency for PR lint runs. |
| .github/workflows/Action-Test.yml | Pins matrix OS runners to ubuntu-24.04, windows-2025, and macos-15 (removes all *-latest). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Brings this repository's inline CI workflows into line with the organization's GitHub Actions coding standard. Runner images are now pinned to specific versions so a runner upgrade is a deliberate, reviewable change, and release runs queue instead of aborting mid-publish.
Changed: runner images are pinned
No workflow uses a
-latestrunner any more; everyruns-onnames a specific image.Action-Test.yml— matrix pinned toubuntu-24.04,windows-2025,macos-15Linter.yml—ubuntu-24.04Release.yml—ubuntu-24.04Changed: release runs queue instead of cancelling
Release.ymlnow setscancel-in-progress: false, so a release that is publishing queues behind an in-flight run rather than being aborted mid-write.Action-Test.ymlandLinter.ymlkeepcancel-in-progress: true, since cancelling a superseded test or lint run is desirable and is not a publish action.Technical Details
Validated locally with
actionlint(0 issues) on all three workflows; the linter workflow re-checksactionlintin CI.These workflows are seeded from Template-Action; the same corrections should also land there so regenerated repositories stay compliant (tracked under Process-PSModule#360).
Dependabot update grouping and semver update labels are intentionally out of scope (see MSXOrg/docs#19 and PSModule/Process-PSModule#359).