chore(deps): bump redb from 3.1.3 to 4.1.0 in /czech-file-knife

[dependabot]

Bumps redb from 3.1.3 to 4.1.0.

Release notes

Sourced from redb's releases.

4.1.0

This release contains a large number of bug fixes discovered by AI coding agents

• Fix a bug where MultimapValue::len() and is_empty() returned stale counts after consuming entries via next_back().
• Fix a bug where restore_savepoint() used in a non-Immediate durability transaction and when there are persistent savepoints newer than the one being restored, could fail with SavepointError::InvalidSavepoint, but the savepoint would actually be partially applied. The call now fails up front with SavepointError::ImmediateDurabilityRequired.
• Fix a bug in restore_savepoint() where modifications made earlier in the transaction might not be reverted.
• Fix a bug where renaming a table that was already modified in the same transaction could cause the database to become corrupted.
• Fix a bug where calling restore_savepoint() after modifying a table in the same transaction could cause the table to become corrupted in a future transaction.
• Fix a panic when delete_table() was called on a table that had been modified in the same transaction.
• Fix a panic in restore_savepoint() when passed a Savepoint from a different Database. SavepointError::InvalidSavepoint is now returned instead.
• Fix a bug where a transaction that created a persistent savepoint and was then aborted could cause the database file to grow excessively, until the Database was dropped.
• Fix a panic in check_integrity() when called while another transaction is still alive. DatabaseError::TransactionInProgress is now returned instead.
• Fix a bug where aborting a transaction that called restore_savepoint() with a savepoint when a newer savepoint existed could cause database space to be leaked.
• Fix a bug where aborting a transaction that called restore_savepoint() would leave more recent savepoints invalid.
• Improve performance when reading concurrently from multiple threads. Around 15% speedup on some benchmarks.
• Optimize cache usage, and general write performance. Around 1.5x speedup on some benchmarks.
• Optimize memory usage.
• Other performance optimizations.

4.0.0

• Implement Drop on AccessGuardMut and AccessGuardMutInPlace, which requires that these be dropped before the Table they borrow from. This fixes a critical bug where the accessor could outlive the Table, and be dropped after the transaction had already committed. This could cause data loss due to the data in the accessor being written out after the transaction had already completed.
• Remove Legacy type. To migrate off the Legacy type, use the Legacy type in the 3.x release and copy the data to a table with plain tuples, before upgrading to the 4.x release.

Changelog

Sourced from redb's changelog.

4.1.0 - 2026-04-19

This release contains a large number of bug fixes discovered by AI coding agents

• Fix a bug where MultimapValue::len() and is_empty() returned stale counts after consuming entries via next_back().
• Fix a bug where restore_savepoint() used in a non-Immediate durability transaction and when there are persistent savepoints newer than the one being restored, could fail with SavepointError::InvalidSavepoint, but the savepoint would actually be partially applied. The call now fails up front with SavepointError::ImmediateDurabilityRequired.
• Fix a bug in restore_savepoint() where modifications made earlier in the transaction might not be reverted.
• Fix a bug where renaming a table that was already modified in the same transaction could cause the database to become corrupted.
• Fix a bug where calling restore_savepoint() after modifying a table in the same transaction could cause the table to become corrupted in a future transaction.
• Fix a panic when delete_table() was called on a table that had been modified in the same transaction.
• Fix a panic in restore_savepoint() when passed a Savepoint from a different Database. SavepointError::InvalidSavepoint is now returned instead.
• Fix a bug where a transaction that created a persistent savepoint and was then aborted could cause the database file to grow excessively, until the Database was dropped.
• Fix a panic in check_integrity() when called while another transaction is still alive. DatabaseError::TransactionInProgress is now returned instead.
• Fix a bug where aborting a transaction that called restore_savepoint() with a savepoint when a newer savepoint existed could cause database space to be leaked.
• Fix a bug where aborting a transaction that called restore_savepoint() would leave more recent savepoints invalid.
• Improve performance when reading concurrently from multiple threads. Around 15% speedup on some benchmarks.
• Optimize cache usage, and general write performance. Around 1.5x speedup on some benchmarks.
• Optimize memory usage.
• Other performance optimizations.

4.0.0 - 2026-04-02

• Implement Drop on AccessGuardMut and AccessGuardMutInPlace, which requires that these be dropped before the Table they borrow from. This fixes a critical bug where the accessor could outlive the Table, and be dropped after the transaction had already committed. This could cause data loss due to the data in the accessor being written out after the transaction had already completed.
• Remove Legacy type. To migrate off the Legacy type, use the Legacy type in the 3.x release and copy the data to a table with plain tuples, before upgrading to the 4.x release.

Commits

• 6ed1f98 Bump version to 4.1.0
• 0a87cb7 Update changelog
• 03966a5 Require callers of get_page to provide a PageHint
• a75927f Remove some TODO comments
• a39779b Avoid allocating a page for a branch that will be immediately merged
• 6374134 Document that Table{,Multimap}Definition::new panic on empty names
• ba043e3 Avoid copying keys in leaf overwrite paths
• f42c468 Fix MultimapValue::next_back() not decrementing remaining counter
• 3756148 Clarify API contract for Key and Value traits
• 4552372 Consolidate WriteTransaction savepoint lifecycle state
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)