build: verify the schemes archive against pinned sha256 - #25
Merged
Conversation
The commit pin already fixes the content upstream; the hash closes the transport — a tampered or truncated archive fails before themes.json is rebuilt. Signed-off-by: Daniil Antoshin <daniil.antoshin@flant.com>
danilrwx
enabled auto-merge (squash)
August 10, 2026 10:24
danilrwx
disabled auto-merge
August 10, 2026 10:26
danilrwx
enabled auto-merge (squash)
August 10, 2026 10:30
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.
One archive, one pin: the tinted-theming tarball downloads to a temp file, must match its sha256, and only then feeds the themes.json build. Verified with
FORCE=1.