Skip to content

fix: use @latest in update install command and clear cache on postinstall#45

Merged
CodesMcCabe merged 1 commit intomainfrom
cm/update-fix
Apr 1, 2026
Merged

fix: use @latest in update install command and clear cache on postinstall#45
CodesMcCabe merged 1 commit intomainfrom
cm/update-fix

Conversation

@CodesMcCabe
Copy link
Copy Markdown
Collaborator

@CodesMcCabe CodesMcCabe commented Apr 1, 2026

Summary

  • Changes the suggested update command from npm i -g @alchemy/cli to npm i -g @alchemy/cli@latest so npm is forced to resolve and fetch the newest published version instead of short-circuiting when it thinks the requirement is already satisfied.
  • Clears the ~/.config/alchemy/.update-check cache file during postinstall, preventing stale "update available" notices from persisting after a successful upgrade.

Test plan

  • All unit tests updated and passing (17/17)
  • Build succeeds
  • Verify npm i -g @alchemy/cli@latest correctly upgrades the CLI
  • Verify the update notice no longer appears after a fresh install

Made with Cursor

…tall

Ensures npm actually fetches the newest version when upgrading, and
clears the update-check cache during postinstall so stale "update
available" notices don't persist after a successful upgrade.

Made-with: Cursor
@CodesMcCabe CodesMcCabe requested a review from a team as a code owner April 1, 2026 00:25
@CodesMcCabe CodesMcCabe merged commit 676ba5c into main Apr 1, 2026
7 checks passed
@CodesMcCabe CodesMcCabe deleted the cm/update-fix branch April 1, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants