chore(memory_strategy): use DeserializeOwned for modify #101
DestinyofYeet
commented
Owner
No description provided.
DestinyofYeet
added 1 commit 2026-09-13 14:57:31 +02:00
chore(memory_strategy): use DeserializeOwned for modify
Some checks failed
Build / build (pull_request) Has been cancelled
Details
Check / check_commit_format (pull_request) Has been cancelled
Details
Check / check_cargo_lock (pull_request) Has been cancelled
Details
DestinyofYeet
added 1 commit 2026-09-13 14:59:57 +02:00
chore(version): bump
All checks were successful
Build / build (pull_request) Successful in 1m24s
Details
Check / check_commit_format (pull_request) Successful in 28s
Details
Check / check_cargo_lock (pull_request) Successful in 15s
Details
Upload to crates.io / check_tag (push) Successful in 5s
Details
Upload to crates.io / publish_macro (push) Successful in 2m11s
Details
Upload to crates.io / publish_db_core (push) Successful in 3m44s
Details
Upload to crates.io / publish_db_sqlite (push) Successful in 1m46s
Details
Upload to crates.io / publish (push) Successful in 1m44s
Details
DestinyofYeet
scheduled this pull request to auto merge when all checks succeed 2026-09-13 15:00:02 +02:00
DestinyofYeet
merged commit a475b5f04c into main
No reviewers
Labels
No labels
priority
high
priority
low
priority
medium
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
DestinyofYeet/dataloom!101
Loading…
Reference in a new issue
No description provided.
Delete branch "develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?