chore(release): bump version to 0.11.0 and rebuild dist - #124
Merged
Conversation
Ships the first user-facing change since 0.10.1: svd_invert now throws on non-square input instead of silently returning a wrong pseudo-inverse (#102). That guard has been on dev but unreleased — verified absent from both the 0.10.1 source and its published bundle — so npm users are still getting the silent garbage it was written to stop. Minor rather than patch because a throw where a value used to come back is a behaviour change, and it is registered in tests/divergences.test.ts. Also ships the LGPL banner in dist/jsfeatNext.js and dist/jsfeatNext.mjs (#112). The published bundles carried no licence notice at all before. Everything else since 0.10.1 is tests and docs — the #87 work took the suite from 60 parity-only cases to 257 across four layers, plus a global buffer-pool leak check and docs/implementation-notes.md. Valuable to the project, invisible to consumers, and deliberately not the reason for the release. The banner version comes from package.json, so the rebuilt bundles carry v0.11.0 automatically. Lockfile regenerated with npm 11 per MAINTAINERS.md. Verified: prettier clean, tsc --noEmit clean, license-check clean, npm test 256 passed + 1 expected fail, and both rebuilt bundles load and run — the svd_invert guard confirmed present in the UMD build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Release prep for 0.11.0, per Phase A of
MAINTAINERS.md.What actually ships to users
svd_invertnow throws on non-square input (#102) instead of silently returning a wrong pseudo-inverse.This is the headline, and it is overdue: the guard has been on
devbut unreleased. Verified absent from both the 0.10.1 source and its published bundle, so anyone on npm today still gets the silent garbage it was written to prevent.Minor rather than patch, because a throw where a value previously came back is a behaviour change. It is registered in
tests/divergences.test.tsas a deliberate divergence from jsfeat.The LGPL banner in the bundles (#112).
dist/jsfeatNext.jsanddist/jsfeatNext.mjspreviously carried no licence notice at all.What does not ship to users
Everything else since 0.10.1 is tests and docs. The #87 work took the suite from 60 parity-only cases to 257 across four layers, added a global buffer-pool leak check and
docs/implementation-notes.md— enormously valuable to the project and completely invisible to consumers. Deliberately not the reason for this release.Worth stating plainly so the release is not mistaken for shipping the test work.
Steps followed
package.jsonnpx npm@11 install), per the note inMAINTAINERS.mdabout older npm omitting cross-platform native binaries and breakingnpm cinpm run build-ts—dist/andtypes/rebuilt; the banner reads the version frompackage.json, so both bundles now sayv0.11.0with no manual editnpx git-cliff --unreleased --tag 0.11.0 --prepend CHANGELOG.mdVerification
prettier clean ·
tsc --noEmitclean ·license-checkclean ·npm test256 passed + 1 expected fail.Both rebuilt bundles were loaded and exercised, with the
svd_invertguard confirmed present in the UMD build:After this merges
Phase A step 6 onward is yours: promote
devtomain, then tag0.11.0(bare, nov) to trigger the release workflow.🤖 Generated with Claude Code