chore(release): v0.1.3 - #10
Merged
Merged
Conversation
Reconciles this package with npm, which has been ahead of git.
npm serves 0.1.2, but no commit ever set that version — it was bumped in a
scratch worktree, published from there, and the bump was never committed.
That left `main` reading 0.1.1 while the registry served 0.1.2, so the repo
could not be published at all: its version was already taken.
Meanwhile main accumulated work that reached no published build:
- `--timeout MS`, threading timeoutMs through lookupMoshpit()
- `--console URL` and `--parking URL`
- validation for all four value-taking flags, so `--registry` with no URL
is an error instead of silently consuming the next flag as its value
0.1.3, skipping the orphaned 0.1.2. Purely additive — the export list is
byte-identical to the published build, nothing removed or renamed.
Verified against the packed tarball, not the source tree: version 0.1.3,
--help lists the new flags, --timeout abc and a valueless --registry are
both rejected, and a live --json resolve works. 27 tests, 27 pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ThreatCrush Security Scan0 finding(s) No findings. |
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
1 participant
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.
Reconciles this package with npm, which has been ahead of git.
The inconsistency
npm serves
0.1.2, but no commit ever set that version. I found the missing bump sitting uncommitted in a scratch worktree — someone bumped it there, published from it, and never committed:So
mainread0.1.1while the registry served0.1.2, which meant the repo could not be published at all — its own version was already taken.What was stranded
Work on
mainthat reached no published build:--timeout MS, threadingtimeoutMsthroughlookupMoshpit()--console URLand--parking URL--registrywith no URL errors instead of silently swallowing the next flag as its valueVersioning
0.1.3, skipping the orphaned0.1.2.Purely additive — I diffed the public export list against the published build and it is identical. Nothing removed, nothing renamed.
resolutionForanddestinationForboth still exist.Verified from the packed tarball
Not the source tree — the actual
.tgz:0.1.3--helplists--console,--parking,--timeout--timeout abc→--timeout must be a positive integer in milliseconds--registrywith no value →--registry requires a URL--jsonresolve works27 tests, 27 pass, 0 fail.Publishing to npm once this merges.
🤖 Generated with Claude Code