chore(release): bump version to 0.14.0 and rebuild dist - #172
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.
Phase A of the release runbook (MAINTAINERS.md)
package.jsonversion 0.13.0 → 0.14.0 (minor: substantial work, no public API break — only additive types from matrix_t re-allocates a data_type lookup table on every construction #159'sshared_data_typeexport).package-lock.jsonwith npm 11.dist/jsfeatNext.js,dist/jsfeatNext.mjs,types/.CHANGELOG.mdvia git-cliff.What's in this release
Everything merged since 0.13.0: #86 phases 2–3 (per-module benchmark suite, CI smoke gate + typecheck scope fix for #157), three real performance fixes found through profiling (#159
data_typesingleton, #165invert_3x3EPSILON hoist, #166 YAPE helper aliasing), and a small README cleanup (#154).Verification
npm test: 265 passed.npm run typecheck,npm run format-check,npm run build-tsall clean.npm auditflags one pre-existing high-severity advisory inbrace-expansion, three levels belowtypedoc(a devDependency) — the published package has zero runtimedependencies, so this does not affect consumers. Not addressed here; flagging for awareness.Once merged, next step is promoting
dev→mainand tagging0.14.0per Phase B.🤖 Generated with Claude Code