doctor, help, update: announce newer ark releases - #20
Merged
Merged
Conversation
Co-authored-by: Astra <noreply@openai.com> Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Adds a release check to every command. At most once an hour, a detached copy of ark reads the newest release from GitHub. While a newer one exists, each command starts with a note naming the upgrade, also without a terminal and under --json.
ark doctorreports it as anupdatecheck that warns without failing, and a nonemptyCIturns it all off.The detached spawn and the development-build request have no tests, since both would reach GitHub. The spawn was checked by hand on macOS, the development request only with curl, and the Windows spawn flags compile but have not run.