Repository navigation
feat(update): clarify installation progress and release guidance - #142
Merged
Merged
Conversation
Make Altertable CLI self-updates easier to scan with styled current and target versions, explicit upgrade/reinstall/downgrade outcomes, and release notes, issue-reporting, and commit-log links. Use Altertable CLI consistently in update messages. Keep JSON results free of human progress output and omit version comparisons when reinstalling the same release.
leonkenneth
approved these changes
Oct 14, 2026
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.
What
Give
altertable updatea Bun-inspired display with styled target and current versions, a clear installation outcome, and links to release notes, bug reports, and the commit log. Use “Altertable CLI” consistently in update messages.For example, upgrading from 1.11.0 to 1.12.0 now shows:
Forced reinstalls and downgrades explicitly say “Reinstalling”/“Reinstalled” and “Downgrading”/“Downgraded”. Reinstalls omit the empty version comparison. The display has no elapsed-time or welcome row. JSON installation results retain their existing shape and no longer include human progress messages.
Why
The previous output only announced the target version and printed a dim installation confirmation. Showing both versions makes the transition easier to scan, and the release links give users useful next steps after installation. Naming the actual action avoids suggesting that a newer release exists during a forced reinstall or downgrade.