feat(update): Add secure CLI self-update - #7
Merged
Merged
Conversation
Operators can check for releases and update the installed CLI in place. Release archives are verified before replacement so a failed or altered download leaves the current binary intact.
Operators can install a verified release with one command without manually selecting an operating system or architecture.
Pull requests now install and execute a pinned published release so changes cannot silently break the public installation path.
CI now installs the published CLI into the standard system location on Ubuntu and runs it from the shell path.
The CLI release follows its own maintenance cadence because these changes improve installation and operations without expanding its product surface.
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.
Operators currently have to download and replace CLI binaries manually. This adds an in-place update path that preserves stable and prerelease channels and refuses unverified release archives.