feat: add update notification to CLI for available package updates#10
Merged
Merged
Conversation
ABujalance
approved these changes
Apr 6, 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
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.
Add update notification to CLI
Description:
Summary
Adds a non-blocking update notifier to the
thatopenCLI. When an outdated version is installed, users will see a notice at the end of any command's output prompting them to update.What changed
fetchrequest checks the latest published version ofthatopen-serviceson the npm registry.process.on('exit')), so it never interrupts normal output.AbortSignal.timeout) and fails silently — no network access or registry errors will ever affect CLI behaviour.Example output
Notes
fetch(available since Node 18+).latesttag, this is sufficient for the intended use case.