Verify downloaded CLI artifacts before execution - #60
Merged
Conversation
axelniklasson
approved these changes
Aug 25, 2026
axelniklasson
left a comment
axelniklasson
left a comment
Contributor
There was a problem hiding this comment.
Didn't run through the full flow locally but code changes look sound to me!
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
2 participants
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.
Summary
Verify the SHA-256 checksum of CLI releases published after v0.16.0 before making the downloaded binary executable. Existing CLI versions, action inputs, and defaults continue to work as they do today.
Future releases fail safely if they are mutable, missing checksum metadata, or do not match the published checksum.
Paired CLI publishing change: linear/linear-release#130
Related: LIN-82854 and #59