Repository navigation
opskit go: pre-launch opencode upgrade check + launch handoff message (#444) - #445
Merged
growlf merged 3 commits intoOct 13, 2026
Merged
Conversation
growlf
deleted the
444-opskit-go-pre-launch-opencode-upgrade-check-launch
branch
October 13, 2026 23:31
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.
Closes #444
Summary
opskit gonow offers an opencode upgrade before launching, when theinstalled version is older than the latest
anomalyco/opencodedev-channel tag.
~/.opskitfor~a day (or until the installed version changes). The actual upgrade is
delegated to
opencode upgrade— opencode is its own oracle.Tests
tests/test_opencode_upgrade.py(22 tests): version/tag parsing, semvercomparison, cache staleness, offer behavior on/offline, and the launch
handoff line.
make test: 1707 passed, 1 skipped.