Update mathjs 14.0.0 → 14.0.1 (patch) #622
Closed
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ mathjs (14.0.0 → 14.0.1) · Repo · Changelog
Release Notes
14.0.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
chore: publish `v14.0.1`
chore: update devDependencies
chore: refactor the benchmarks to use `tinybench`
chore: add `eigen` to the matrix_operations.js benchmark. Switch to `tinybench` to make that work
chore: update HISTORY.md
fix: export `Fraction` type from the `fraction.js` library instead of using custom one (#3330)
chore: remove CI testing with HyperExecuted (LambdaTest)
chore: do not cancel browserstack tests which are in progress
chore: trigger a concurrent test run
chore: set concurrency for browserstack tests to 1
chore: update history
fix: make derivative much faster (#3322)
chore: revert LambdaTest browser config again (not yet working)
chore: update LambdaTest browser config
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands