Repository navigation
chore: bump version to 1.4.0 - #16
Merged
Merged
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
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.
Release 1.4.0. Minor rather than patch, because #15 adds user-visible behaviour.
What ships
#15 — failure diagnostics in
test:fail. A CLI failure now names the route the test was on and which mock rules never fired:#14 — dependency bumps to a clean audit.
npm audit4 high → 0.vite8.2.2,vitest5,ws8.21.3,esbuild0.28.2,happy-dom20.14.0, plus afast-urioverride. All dev-only; the published package's sole runtime dependency is stillws.Note on the diagnostics block
It stays dormant until twd-js publishes the release carrying BRIKEV/twd#335. Users who install 1.4.0 before that get no behaviour change —
test.diagnosticsis undefined, so the block is simply absent. It starts appearing once the new twd-js is installed, with no further relay change and no peer-range bump.Verification
npm run test:ci→ 96/96 passing, 11 filesnpx tsc --noEmit→ cleannpm run build→ OK; 3 rolled-up.d.ts, 0 stub filesnpm audit→ 0 vulnerabilitiesnpm pack --dry-run→dist/contents as expected, all three entry points pluscli.jsVersion bumped by editing
package.jsonand runningnpm install; the lockfile diff is the two version fields only.🤖 Generated with Claude Code