Repository navigation
craft: update release pins - #2
Merged
Merged
Conversation
Generated by .github/workflows/update-pins.yml (nix run .#update -- --all). Hashes come from each release's SHA256SUMS.txt; product metadata, which this job never touches, lives in products.nix.
mahlquistj
enabled auto-merge (squash)
October 19, 2026 11:50
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.
New upstream releases
Generated by the scheduled
nix run .#update -- --all— no Nix buildwas needed: each hash is the release's own SHA256SUMS.txt line, converted
with
nix hash convert. Onlypins.lock.jsonchanges;products.nix(asset naming, wrapper flags) is untouched by this job.
Before merging
nix flake check(the flake check job) covers the eval test acrossx86_64/aarch64/riscv64, the twelve headless
<app>-cli --versionsmoketests, upstream's desktop/AppStream validation and the NixOS module contract.
<release version>, and themetainfo check compares it against these pins, so a mislabelled asset
fails here rather than shipping.