v1.119.1: CI maintenance (attest migration + windows-2025 pin)#56
Merged
Conversation
Clears the two non-blocking annotations the release workflow was emitting, ahead of GitHub's deadlines. CI-only; no functional change to the tool. - actions/attest-sbom -> actions/attest: the SBOM-attestation action was deprecated. actions/attest exposes a native sbom-path input (SPDX/CycloneDX, auto-detected) that maps 1:1 from the old action and produces an identical SBOM attestation, still verifiable via `gh attestation verify`. Pinned to 59d89421af93a897026c735860bf21b6eb4f7b26 (v4.1.0). Added the artifact-metadata: write permission that actions/attest v4 documents. - windows-latest -> windows-2025 in ci.yml + powershell-scan.yml: GitHub redirects windows-latest to the Server 2025 image by 2026-06-15. Pinning now makes the runtime explicit and validates the build against the target image. windows-2025 ships Windows PowerShell 5.1 + .NET FW 4.8 + pwsh 7 — all the pipeline needs (it never invokes the VS toolchain, so the VS2026 change is irrelevant). GOVERNANCE.md updated to match. Researched + adversarially verified against official GitHub sources (attest migration is a drop-in input swap; artifact-metadata is a valid scope; SHA matches v4.1.0). 81 modules, 201 actions unchanged; 5167 tests green.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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.
v1.119.1 — CI maintenance
Clears the two non-blocking annotations the release workflow was emitting, ahead of GitHub's deadlines. CI-only; no functional change to the tool.
actions/attest-sbom→actions/attest— the SBOM-attestation action was deprecated.actions/attestexposes a nativesbom-pathinput (SPDX/CycloneDX, auto-detected) that maps 1:1 from the old action and produces an identical SBOM attestation, still verifiable viagh attestation verify. Pinned to59d89421…(v4.1.0). Added theartifact-metadata: writepermissionactions/attestv4 documents.windows-latest→windows-2025(ci.yml+powershell-scan.yml) — GitHub redirectswindows-latestto the Server 2025 image by 2026-06-15. Pinning now makes the runtime explicit and validates the build against the target image.windows-2025ships Windows PowerShell 5.1 + .NET FW 4.8 + pwsh 7 — all the pipeline needs (it never invokes the VS toolchain, so the concurrent VS2026 image change is irrelevant).GOVERNANCE.mdupdated to match.Researched + adversarially verified against official GitHub sources: the attest migration is a drop-in input swap,
artifact-metadatais a valid permission scope, and the SHA matches v4.1.0. The runner change is exercised by this PR'stest+powershell-scanchecks (both now onwindows-2025); the attest step is exercised on the post-merge release run.81 modules, 201 CLI actions unchanged; 5167 structural tests green.