Bump LiteDB from 4.1.4 to 5.0.11

[dependabot-preview[bot]]

Bumps LiteDB from 4.1.4 to 5.0.11.

Release notes

Sourced from LiteDB's releases.

v5.0.11

Bugfixes

• #1275
• #1772
• #1956
• #2021
• #2023

v5.0.10

Bugfixes

• Fix invalid multi-page CString reader
• Fixed issue when checkpoint soft limit not applied for manual transaction

ENSURE in Release mode

• This new 5.0.10 contains an adicional test layer called ENSURE used in all storage/cache layer. Until now, this tests was executed only in DEBUG mode but now we add into RELEASE mode too. If any ENSURE are violated a system exception will be throwed (prefix message "LiteDB ENSURE:"). This will better for detect and prevent data corruption database and much better diagnostics and bugfixes. Complex tests (like check if a byffer is empty) still run in DEBUG mode only to avoid performance down.

v5.0.9

Changes

• The LiteDatabase ctor that takes a Stream for its data storage now takes another Stream as log storage. LiteDB can now be used with custom storage solutions (as long as it implements Stream).
• Custom serializers and deserializers can now be used even with basic BSON types. This is useful if you don't want to lose precision when storing DateTime.

Bug fixes

• #1684
• #1685
• #1695
• #1701
• #1735
• #1740
• #1754
• #1761
• #1774
• #1777

v5.0.8

Bug fixes

• #1630
• #1633
• #1636
• #1638
• #1650
• #1651
• #1656
• #1664
• #1665
• #1668
• #1678
• #1681

v5.0.7

... (truncated)

Commits

• 6520f09 Increment version to 5.0.11
• 2fbcea0 Merge pull request #2036 from mbdavid/wal_empty_page_workaround
• 0addd62 Style fixes
• 1198ffc Removing unused array
• 6ed91b6 Optimized workaround for blank pages in the log file
• 9f10dbb Workaround for zeroed pages in the log file
• 0eb1f5f Indexes over bool fields are now created with the correct expression
• 2db51be Fixed serialization for relative URIs
• 5ec64e5 LiteDB now correctly initializes zero-byte files
• 88233d0 Fix for long index names on upgrade
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)