Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

Releases: lostatc/acid-store

v0.14.1

15 Jul 21:44
16c40fc
Compare
Choose a tag to compare
v0.14.1 Pre-release
Pre-release
  • Upgraded dependencies.
  • Increased MSRV to 1.70.0.

v0.14.0

23 Jun 04:40
40b238b
Compare
Choose a tag to compare
v0.14.0 Pre-release
Pre-release

v0.13.1

28 Mar 21:46
aa79401
Compare
Choose a tag to compare
v0.13.1 Pre-release
Pre-release
  • Upgrade rmp-serde

v0.13.0

06 Jan 15:02
dbb750b
Compare
Choose a tag to compare
v0.13.0 Pre-release
Pre-release
  • Add an MSRV to Cargo.toml and an MSRV policy to the README.
  • Add a semver policy to the README.
  • Remove anyhow from the public API and replace it with crate::store::Error.

v0.12.1

25 Sep 00:02
18b310f
Compare
Choose a tag to compare
v0.12.1 Pre-release
Pre-release
  • If duplicate mount options are passed to FileRepo::mount, deduplicate them before passing them to libfuse.

v0.12.0

21 Sep 04:16
1cb9d08
Compare
Choose a tag to compare
v0.12.0 Pre-release
Pre-release
  • Added support for v3.x of libfuse via the fuser crate.
  • Changed the API for mounting a FUSE file system slightly to make passing mount options easier.
  • Updated several dependencies.

v0.11.3

14 Sep 01:31
a7796b7
Compare
Choose a tag to compare
v0.11.3 Pre-release
Pre-release
  • Update dependency versions

v0.11.1

23 Nov 19:21
8ba8c9a
Compare
Choose a tag to compare
v0.11.1 Pre-release
Pre-release
  • Fix bug opening an existing DirectoryStore (#9)

v0.11.0

22 Aug 15:47
08a318c
Compare
Choose a tag to compare
v0.11.0 Pre-release
Pre-release
  • Redesign the DataStore API
  • Add support for two-phase locking to protect against concurrent access
  • Add API for removing stale locks
  • Support linking entries in FileRepo
  • Support hard links when mounting a FileRepo using FUSE

v0.10.0

07 Aug 16:53
632685e
Compare
Choose a tag to compare
v0.10.0 Pre-release
Pre-release
  • Fix some types not being Send and Sync
  • Make it impossible to get an ObjectId when an object has been invalidated
  • Clarify documentation around ContentId and sparse objects
  • Re-export relative_path crate