mirrors/arti.git/crates/fslock-guard, branch arti-v2.4.0

Bump the versions of the non-{arti-,tor-} crates

2026-06-01T16:30:04Z

The non-{arti-,tor-} crates are: ``` ./maint/list-crates | rg -v '^(tor|arti)' oneshot-fused-workaround web-time-compat slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error futures-copy ``` We split them in the following categories: * crates with no changes (no version bumps): ``` oneshot-fused-workaround: No change. web-time-compat: No change. slotmap-careful: No change. test-temp-dir: No change. caret: No change. safelog: No change. retry-error: No change. futures-copy: No change. ``` Obtained with: ``` maint/changed-crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '$tor\|arti$-' ``` * crates that only have non-functional changes (bump the patch version, but not the dependend-on version): - equix * crates where functional changes were made, but no APIs were broken (bump patch): - fs-mistrust * crates where APIs were broken (bump minor): - hashx - fslock-guard The bumps from this commit were created using this script: ``` PATCH_NF=( equix ) PATCH=" fs-mistrust " MINOR=" hashx fslock-guard " ./maint/bump-nodep "${PATCH_NF[@]}" for crate in $PATCH; do cargo set-version --bump patch -p $crate; done for crate in $MINOR; do cargo set-version --bump minor -p $crate; done ```

fslock-guard: Provide specialized android impls.

2026-05-28T14:47:16Z

We need these because `File::lock()` and `File::try_lock()` claim not to work on Android, and have to be emulated with flock. For more information, see . Closes #2544. Based on code by @syphyr. Co-Authored-By: syphyr

fslock-guard: Extract calls to {try_,}lock

2026-05-28T14:46:17Z

We're about to provide android-only versions of these.

fslock-guard: Use windows-sys and GetFileInformationByHandleEx.

2026-05-12T17:23:12Z

Unlike winapi, windows-sys is maintained (by microsoft), and supports more APIs. We use it elsewhere in our tree, but this was our largest usae of winapi. The GetFileInformationByHandleEx variant includes an explicit buffer size to make errors harder, and enables us to get a 128-bit file identifier, which is (supposedly) even more unique than the 64-bit identifiers we were looking at before.

fslock-guard: add a fileapi feature dep for winapi

2026-05-11T13:10:51Z

With dropping the fslock crate, we lost this feature flag from _its_ use of winapi.

fslock-guard: Fix up documentation a bit.

2026-05-06T19:28:40Z

This mainly amounts to clarifying some of our windows desiderata, and removing the final refrences to fslock.

fslock-guard: Compile on wasm.

2026-05-06T19:28:40Z

We can't actually open a file on wasm-unknown-unknown, but it's more convenient for us if we don't have to conditionally compile this crate every place that uses it.

fslock-guard: Remove fslock dependency.

2026-05-06T19:28:40Z

We can do this since our msrv is now 1.89.0, where File::lock is supported.

Bump the versions of the non-{arti-,tor-} crates

2026-03-02T17:36:23Z

The non-{arti-,tor-} crates are: ``` ./maint/list-crates | rg -v '^(tor|arti)' oneshot-fused-workaround slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error futures-copy ``` Because this release bumps the MSRV, I am bumping the minor version of all of them. MINOR=" oneshot-fused-workaround slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error futures-copy " for crate in $MINOR; do cargo set-version --bump minor -p $crate; done ```

Allow clippy::collapsible_if to trigger

2026-02-16T15:22:24Z

`clippy::collapsible_if` started triggering after bumping the MSRV to 1.88. Since this triggers from a lot of places, and since there even are a couple of instances where we explicitly allow `clippy::collapsible_ifs`, I've opened #2342 for deciding what to do about it.