feat: add startup version check to warn users of outdated CLI #35
Conversation
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
Checks npm registry for latest version on startup and displays a warning if the current version is outdated, suggesting `npx workos@latest`. - Blocks up to 500ms for the check before any commands run - Fails silently on network errors or timeouts - Uses semver for version comparison
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.
Summary
npx workos@latestcommand when running outdated versionWhy
Users running
npx workosreceive cached, outdated versions due to npx caching behavior. The cache stores the first downloaded version indefinitely, causing users to unknowingly run deprecated versions (e.g., v0.0.24) instead of current (v0.3.2). This leads to bugs, missing features, and API incompatibilities.Notes
semverdependency for version comparison