Repository navigation
Conversation
fengmk2
force-pushed
the
fix/verify-installer
branch
from
October 8, 2026 06:03
ad25c27 to
1c8d652
Compare
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.
Installer downloads previously ran without integrity checks. A compromised download source could execute code on CI runners.
GitHub Actions, GitLab, and Azure now check installer scripts against bundled
SHA-256checksums before execution. Download URLs use immutable upstream commits. The checks also cover mirrors and legacy helpers.Known versions keep their matching installer. Dist-tags, preview builds, and unknown versions use a default installer with a bundled checksum. If all version-specific sources fail, installation also uses this default. Changes to installer scripts require a
setup-vpupdate.