Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -735,15 +735,15 @@ hunting for the wrong things.

Plan §1 goal-4 ("no regression on CLI hot path vs the v0.5.35
baseline") verified end-to-end on the Windows 7-drive reference
box. Current v0.5.99 (post-Phase-8 tiered architecture) is
box. Current v0.5.100 (post-Phase-8 tiered architecture) is
**universally faster** than v0.5.35 across every benchmarked
pattern, with the largest result set (`*.dll`, 44 529 rows)
showing a **2.7× speedup**:

```
Drive D, 7.07 M records, 30 rounds, HOT phase, p50 / p95 wall_ms:

v0.5.35 v0.5.99 Δ p50
v0.5.35 v0.5.100 Δ p50
exact (3 rows) 20 / 23 → 18 / 19 −10 %
prefix (8 732) 46 / 50 → 40 / 46 −13 %
ext_rare (11) 18 / 20 → 17 / 18 −6 %
Expand Down Expand Up @@ -919,7 +919,7 @@ log-message renames fail CI before reaching another 24-h soak.
2026-05-13. No new operator-surface features land on `main`
until v0.6.0 ships.

## [0.5.99] - 2026-05-08
## [0.5.100] - 2026-05-08

> **Note on the v0.5.91 gap.** v0.5.91 was prepared and tagged but never
> reached a published GitHub Release: the `release.yml` finalize step hit
Expand All @@ -928,7 +928,7 @@ log-message renames fail CI before reaching another 24-h soak.
> partial release was deleted, the tag name became permanently locked by
> GitHub's *immutable releases* feature (the pre-receive hook refuses any
> future ref creation under that name even after a clean delete). The
> public release sequence therefore jumps `v0.5.90 → v0.5.99`; all
> public release sequence therefore jumps `v0.5.90 → v0.5.100`; all
> intended v0.5.91 changes are rolled forward into this release.

### Fixed
Expand Down
42 changes: 21 additions & 21 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

20 changes: 10 additions & 10 deletions Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ members = [
# Workspace Package Metadata (inherited by all crates)
# ─────────────────────────────────────────────────────────────────────────────
[workspace.package]
version = "0.5.99"
version = "0.5.100"
edition = "2024"
# MSRV: Pure Rust code compiles on stable 1.91+ (Duration::from_mins),
# but Polars is built with features = ["nightly", "simd"] which requires
Expand Down Expand Up @@ -116,21 +116,21 @@ publish = false
# proposed-plan output for 12 days because `release-plz update`
# failed at `cargo package` with this very error. See
# `release-automation-baseline.md` §10 for the diagnostic trail.
uffs-polars = { path = "crates/uffs-polars", version = "0.5.99" }
uffs-security = { path = "crates/uffs-security", version = "0.5.99" }
uffs-text = { path = "crates/uffs-text", version = "0.5.99" }
uffs-time = { path = "crates/uffs-time", version = "0.5.99" }
uffs-mft = { path = "crates/uffs-mft", version = "0.5.99" }
uffs-format = { path = "crates/uffs-format", version = "0.5.99" }
uffs-core = { path = "crates/uffs-core", version = "0.5.99" }
uffs-client = { path = "crates/uffs-client", version = "0.5.99" }
uffs-polars = { path = "crates/uffs-polars", version = "0.5.100" }
uffs-security = { path = "crates/uffs-security", version = "0.5.100" }
uffs-text = { path = "crates/uffs-text", version = "0.5.100" }
uffs-time = { path = "crates/uffs-time", version = "0.5.100" }
uffs-mft = { path = "crates/uffs-mft", version = "0.5.100" }
uffs-format = { path = "crates/uffs-format", version = "0.5.100" }
uffs-core = { path = "crates/uffs-core", version = "0.5.100" }
uffs-client = { path = "crates/uffs-client", version = "0.5.100" }
# `uffs-broker-protocol` carries the wire-protocol types shared between
# `uffs-broker` (the elevated handle vendor, Windows-only binary) and
# `uffs-daemon::broker_client` (the handle consumer). Pure-logic
# Layer-0 lib — cross-platform tests run on every CI lane. Added in
# F5 (issue #205) so neither side duplicates `BROKER_PIPE_NAME` /
# wire-format byte literals.
uffs-broker-protocol = { path = "crates/uffs-broker-protocol", version = "0.5.99" }
uffs-broker-protocol = { path = "crates/uffs-broker-protocol", version = "0.5.100" }
# NOTE: no `uffs-broker` workspace dependency alias on purpose —
# `uffs-broker` is a binary-only crate (the only `[lib]` it carries is
# this protocol module's now-extracted sibling); no other workspace
Expand Down
2 changes: 1 addition & 1 deletion rust-toolchain.toml
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@
# CI pipeline will auto-refresh on `ship --fresh` unless `--skip-toolchain-sync`
# is passed — use that flag (or plain `just ship`) while the upstream regression
# persists.
channel = "nightly-2026-05-15"
channel = "nightly-2026-05-16"

# Specify components that should always be available
components = [
Expand Down
6 changes: 6 additions & 0 deletions supply-chain/audits.toml
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,12 @@ criteria = "safe-to-deploy"
version = "3.1.1"
notes = "Reviewed v3.1.1 source. Scope: ANSI terminal coloring. One unsafe block in control.rs (Windows Console FFI via windows-sys: GetStdHandle / GetConsoleMode / SetConsoleMode) — standard Win32 terminal setup, properly cfg(windows)-gated. No network I/O, no filesystem writes, no process spawning. Only std types plus windows-sys on Windows. Dev-deps (rspec, insta, ansiterm) are standard testing crates. MPL-2.0 licensed, same as our workspace."

[[audits.hashbrown]]
who = "Robert M1 <50460704+githubrobbi@users.noreply.github.com>"
criteria = "safe-to-deploy"
delta = "0.17.0 -> 0.17.1"
notes = "Reviewed 0.17.0 -> 0.17.1 source diff (6 files, +106/-28). (1) CHANGELOG / Cargo.toml{,.orig} / README — version bump (drops redundant 'authors' field) + markdown line-wrap reformat. (2) src/control/group/lsx.rs — 3-line LoongArch SX SIMD micro-opt inside an existing unsafe block: lsx_vslt_b(self.0, zero) -> lsx_vslti_b::<0>(self.0) and lsx_vor_v(special, lsx_vreplgr2vr_b(imm)) -> lsx_vori_b::<imm>(special). Replaces materialized-zero compare with the immediate-compare intrinsic. No new unsafe blocks, no new intrinsics outside the 0.17.0 set, no behavior change to SwissTable special-tag construction. LoongArch is not a shipping target for UFFS (x86_64 + aarch64 only). (3) src/rustc_entry.rs — additive: new HashMap::rustc_try_insert (PR #722) returning Result<&mut V, RustcOccupiedError> for collision-aware insertion, plus the RustcOccupiedError struct. Built on the existing self.table.find / self.table.insert_entry primitives; no new unsafe, no FFI / FS / network / process surfaces. The 'rustc_*' prefix marks it for upstream rustc consumption (hashbrown backs std::collections::HashMap). MIT OR Apache-2.0 (unchanged)."

[[audits.hermit-abi]]
who = "Robert M1 <50460704+githubrobbi@users.noreply.github.com>"
criteria = "safe-to-deploy"
Expand Down
Loading