Add LSTK_UPDATE_CHECK to control the self-update check - #472
Draft
anisaoshafi wants to merge 1 commit into
Draft
Conversation
anisaoshafi
force-pushed
the
allow-disabling-update
branch
from
August 27, 2026 13:13
9e8020b to
ea60205
Compare
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.
Motivation
lstk startchecks for updates and shows a prompt or notice, and does not offer a way to disable update checks completely. This is causing friction for installations managed by external tools.Solution
Two ways to skip or change the check, env var wins over config:
LSTK_UPDATE_CHECKenv varcli.update_checkin config.tomlBoth take
prompt(today's default),notify(one line, no wait), oroff(skips the check entirely).Review
Small, additive, fully tested. Self-merge candidate.
Towards DEVX-1029