Repository navigation
Upgrade leveldb-registry to 2.0.0 and handle ctrl+c gracefully - #310
Merged
Merged
Conversation
viqueen
enabled auto-merge (squash)
November 1, 2026 02:15
Allow classic-level (replaces leveldown) to skip its build script. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Add a shared handleCliError used by every bin entry point so ExitPromptError exits with code 130 instead of printing a stack trace. Other errors are still logged and now set exit code 1. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
viqueen
force-pushed
the
feature/use-latest-leveldb-registry
branch
from
November 1, 2026 02:16
e2f994f to
5824f60
Compare
|
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.
Summary
@labset/leveldb-registryfrom^1.3.0to^2.0.0. No source changes were needed. The new version usesclassic-levelinstead ofleveldown, so it is added toallowBuilds(set tofalse, likeleveldown) inpnpm-workspace.yaml.handleCliErrorso cancelling a prompt with ctrl+c exits quietly with code 130 instead of printing anExitPromptErrorstack trace. It is wired into every bin entry point. Other errors are still logged and now exit with code 1.Test plan
pnpm buildpnpm test(19 passing)handleCliErrorgiven anExitPromptErrorexits 130 with no outputgit recentand confirm there is no stack tracegit workspacecommand against a real registry to confirmclassic-levelloads without its build script (if not, set it totrue)pnpm lintcould not be run:eslint-plugin-import@2.32.0crashes under ESLint 10 (unrelated to this change)🤖 Generated with Claude Code