Update dexie 3.2.4 → 3.2.6 (patch) #3078
Merged
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?
✳️ dexie (3.2.4 → 3.2.6) · Repo
Release Notes
3.2.6
3.2.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
Build output
Merge remote-tracking branch 'origin/releases-3' into master-3
Releasing v3.2.6
Resolve #1883: Exception when having nested index and inserting null value of nested parent.
Build output
Releasing v3.2.5
Merge remote-tracking branch 'origin/releases-3' into master-3
Replace 1n with BigInt(1) for tests on old browsers to run in release script
npm audit fix
Removing a 4.0 test that happened to slip through to 3.x in a cherry-pick operation.
Support BigUint64Array (not just BigInt64Array)
Fix issue with BigInt64Array (#1892)
Added gh-actions for 3x (#1751)
Workaround for UnknownError in Chrome (#543)
Bugfix: Support single-valued compound keys (#1795)
Fix #1740 for Dexie 3x (#1742)
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