Skip to content

fix(upgrade): refuse to guess when no global install is found - #39

Merged
wsehl merged 1 commit into
bstack/wsehl/22d9d0b07a8c45ec931e2d4be2ffc930from
bstack/wsehl/7d973f2bc71943d1afe5fdc49a9c593a
Sep 29, 2026
Merged

wsehl merged 1 commit into
bstack/wsehl/22d9d0b07a8c45ec931e2d4be2ffc930from
bstack/wsehl/7d973f2bc71943d1afe5fdc49a9c593a

Conversation

@wsehl

@wsehl wsehl commented Sep 29, 2026

Copy link
Copy Markdown
Owner

When no package manager listed bstack as a global package (for example
when it runs through npx or pnpm dlx), upgrade fell back to
npm install -g bstack@latest, creating a global install the user never
asked for. It now stops with an error that explains how to get the
latest version instead.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) noreply@anthropic.com

When no package manager listed bstack as a global package (for example
when it runs through npx or pnpm dlx), upgrade fell back to
`npm install -g bstack@latest`, creating a global install the user never
asked for. It now stops with an error that explains how to get the
latest version instead.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
bstack-id: 7d973f2bc71943d1afe5fdc49a9c593a
@wsehl
wsehl added this pull request to stack #43 September 29, 2026 10:33
@wsehl
wsehl merged commit 867d88f into main Sep 29, 2026
1 check passed
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.

1 participant