feat(update): simplify update command behavior and API#64
Merged
Conversation
leonkenneth
approved these changes
Jul 15, 2026
| function validateUpdateArguments(rawArgs: readonly string[]): void { | ||
| let versionSeen = false; | ||
|
|
||
| for (let index = 0; index < rawArgs.length; index += 1) { |
Contributor
There was a problem hiding this comment.
We should probably not need to do this and have readily available parsing library that translates to a structured JSON version
Member
Author
There was a problem hiding this comment.
Yes, will revisit the overhaul architecture of the commands for that
| if (comparison < 0) { | ||
| return [ | ||
| renderDisplayText([ | ||
| span(`Target version v${target} is older than installed altertable v${current}.`), |
Contributor
There was a problem hiding this comment.
Wondering if we should just use https://github.com/vadimdemedes/ink or similar at this point
Member
Author
There was a problem hiding this comment.
Didn't want to go in that direction yet. I think it might be too much for our UI ambitions today
leonkenneth
added a commit
that referenced
this pull request
Jul 16, 2026
🤖 I have created a release *beep* *boop* --- ## [1.3.0](v1.2.0...v1.3.0) (2026-07-16) ### Features * **update:** simplify `update` command behavior and API ([#64](#64)) ([310acdf](310acdf)) ### Bug Fixes * **cli:** ignore unrelated Altertable environment variables ([#67](#67)) ([8fe9041](8fe9041)) * **release:** checkout merge commit for draft release verification ([#58](#58)) ([988c95d](988c95d)) * **release:** run recovery with current publication code ([#63](#63)) ([eab2c4a](eab2c4a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Léo-Paul Goffic <leo.goffic@altertable.ai>
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.
Context
The update command had a Bun-like capability buried behind several flags:
This made the common path verbose and exposed multiple installer, source, cache, and status options that were primarily implementation details. It also produced ambiguous messaging for explicit older versions and could resolve the wrong executable path when a compiled binary was invoked through
PATHor a symlink.Proposed solution
Simplify the public update interface to:
The
upgradealias remains available as a convenience.This change:
altertable updateinstall the latest release by default.--checkfor check-only behavior.--forcefor downgrades or reinstalling the current version.--install--target-version--source--install-method--target-path--status--clear-cache--check-intervalPATHlookups, and symlinked invocations.