{{ message }}
Repository navigation
[release/v7.5.12] Bump PowerShell/compliance/.github/workflows/ready-to-merge.yml from 1.0.0 to 1.0.1 - #28149
Merged
Patrick Meinecke (SeeminglyScience) merged 1 commit intoOct 7, 2026
Conversation
…1.0.0 to 1.0.1 (PowerShell#27338) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Patrick Meinecke (SeeminglyScience)
requested a review
from a team
as a code owner
October 7, 2026 17:28
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
All three dependency annotations must be updated to v1.0.1 to match the pinned commit.
3 open findings
What changed in this PR
Backports the compliance ready-to-merge workflow upgrade to the v7.5.12 release branch.
Changes:
- Pins Linux, macOS, and Windows CI to the v1.0.1 commit.
- Version annotations remain incorrectly labeled v1.0.0.
| File | Description |
|---|---|
.github/workflows/windows-ci.yml |
Updates the compliance workflow SHA. |
.github/workflows/macos-ci.yml |
Updates the compliance workflow SHA. |
.github/workflows/linux-ci.yml |
Updates the compliance workflow SHA. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
| # - analyze | ||
| if: always() | ||
| uses: PowerShell/compliance/.github/workflows/ready-to-merge.yml@c8b3ad5819ad7078f3e375519b4f8c6232d1cbdf # v1.0.0 | ||
| uses: PowerShell/compliance/.github/workflows/ready-to-merge.yml@e051ddbdb7865c0a505ce3bf3b2b7abdb50f79d3 # v1.0.0 |
| - macos_test_unelevated_others | ||
| if: always() | ||
| uses: PowerShell/compliance/.github/workflows/ready-to-merge.yml@c8b3ad5819ad7078f3e375519b4f8c6232d1cbdf # v1.0.0 | ||
| uses: PowerShell/compliance/.github/workflows/ready-to-merge.yml@e051ddbdb7865c0a505ce3bf3b2b7abdb50f79d3 # v1.0.0 |
Aditya Patwardhan (adityapatwardhan)
approved these changes
Oct 7, 2026
Patrick Meinecke (SeeminglyScience)
merged commit Oct 7, 2026
4b18ebc
into
PowerShell:release/v7.5.12
41 checks passed
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.


Backport of #27338 to release/v7.5.12
Triggered by Patrick Meinecke (@SeeminglyScience) on behalf of @app/dependabot
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Updates the PowerShell/compliance ready-to-merge reusable workflow pin in Linux, macOS, and Windows CI workflows.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick completed cleanly. This is a workflow-reference update; no local tests were run. CI must pass on the backport PR before merge.
Risk
REQUIRED: Check exactly one box.
The change modifies CI workflows used by the release branch. It is a narrow pinned-reference update, and successful CI validation is required before merge.