Skip to content

armgit / xerj

Public Imported from GitHub
0

AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.

release: cut 1.0.0-rc.72

xerj-org922fad46c12a
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5e5bd0eda..367f00a84 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,62 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
+## [1.0.0-rc.72] - 2026-08-31
+
+The idle-cost release. A 2026-08-29 measurement session found XERJ was not
+quiet at rest: on a node holding 464 small indices — the shape `xerj autoindex`
+produces from a reference corpus — the process burned 15–27% of a core and 115
+wakeups per second with zero requests, and a 154 MB corpus spent 40+ minutes at
+~110% CPU merging after ingest "finished". Customers reported it as fans
+spinning on an idle laptop. Three of the four mechanisms are fixed here; the
+fourth ([#876](https://github.com/xerj-org/xerj/issues/876)) has a published
+design and is not yet implemented. The budget every fix is held to, and the
+remaining gap, are tracked in the open meta-issue
+[#874](https://github.com/xerj-org/xerj/issues/874).
+
+Alongside it, six Elasticsearch-compatibility and autoindex correctness fixes,
+each shipped with a test proven to fail on the unfixed code.
+
+### Performance
+
+- **An idle index no longer costs a timer, a thread or a wakeup**
+ ([#871](https://github.com/xerj-org/xerj/issues/871)). Every index ran its own
+ `tokio` task that woke every 5 seconds forever and evaluated merge policy
+ whether or not anything had been written — 464 indices meant 93 wakeups per
+ second and two runtime workers each burning ~10% of a core, on a node serving
+ nothing. Merge scheduling is now event-driven, the same shape the WAL fsync
+ scheduler adopted in rc.16 for the identical defect
+ ([#334](https://github.com/xerj-org/xerj/issues/334)): a segments-changed hook
+ fires on every snapshot swap that alters the segment set (flush publication,
+ merge application, tombstone-only segment, orphan recovery) and a debounced
+ request arms at most one check. `XERJ_MERGE_INTERVAL_SECS` keeps its meaning
+ as the debounce delay. Measured at the unit level with an evaluation counter:
+ 768 evaluations across a simulated idle hour become 48.
+
+- **The resource sampler stopped walking every index × every shard lock**
+ ([#872](https://github.com/xerj-org/xerj/issues/872)). The memory breaker's
+ sampler summed memtable bytes every 100 ms by taking a read lock on all 16
+ shards of every index — 74,240 lock acquisitions per second at 464 indices, in
+ one thread, to compute a number that is almost always zero. The aggregate is
+ now maintained incrementally by the write paths that already compute the byte
+ delta, and the sampler is a single relaxed load. The breaker's
+ starvation-immunity property is unchanged: it still runs on a dedicated OS
+ thread, it just no longer does O(indices × shards) work to do it.
+
+- **A multi-index search runs its per-index searches concurrently**
+ ([#875](https://github.com/xerj-org/xerj/issues/875)). The fan-out awaited each
+ index before starting the next, so an `ax-*` query cost the SUM of its
+ per-index latencies instead of the maximum — the shape every reference-coding
+ retrieval uses. Hit ordering, aggregation merge order and the global search
+ permit that bounds concurrency are all unchanged.
+
+ Two behaviour changes worth knowing: `queries_by_index` now increments for
+ every resolvable index even when a later index errors the request (those
+ searches genuinely run now), and per-index deadlines all start at request time
+ rather than sequentially, so a search queued behind the permit pool can return
+ `timed_out: true` with partial results where the serial loop returned complete
+ results slowly.
+
### Fixed
- **A field holding both numbers and strings in one segment no longer loses the
@@ -136,6 +192,85 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
document positions as it has slots (`"a a"` does not match a doc holding
one `a`).
+
+- **A small index reaches a segment instead of living in memory forever**
+ ([#873](https://github.com/xerj-org/xerj/issues/873)). `needs_flush` was
+ threshold-only, so a dataset below the size thresholds never flushed: its
+ documents stayed memtable-resident for the life of the process, pinned their
+ WAL generations on disk, and replayed on every start. Measured on a real
+ corpus: a 100,001-document dataset with zero segments 30+ minutes after
+ ingest. New `storage.flush_idle_secs` (default 300 s, `0` disables) flushes a
+ non-empty memtable whose contents have not changed for that long, detected by
+ a probe on the existing periodic flusher so the write path pays nothing. This
+ matches Elasticsearch's `indices.memory.shard_inactive_time` default.
+
+- **`match_phrase` `slop` admits transposed terms at Lucene's cost of 2**
+ ([#830](https://github.com/xerj-org/xerj/issues/830)). The sloppy-phrase walk
+ was in-order only — each next term had to match strictly after the previous —
+ so `"quick brown"~2` never matched `brown quick`, diverging from Lucene's
+ `SloppyPhraseMatcher`. It is now a minimal-window sweep over adjusted
+ positions, shared by the memtable and segment arms so the answer does not
+ change at flush, and covering `match_phrase`, `match_phrase_prefix` and
+ `multi_match` phrase modes.
+
+- **A date field's epoch scale comes from its mapping, not from each value**
+ ([#790](https://github.com/xerj-org/xerj/issues/790)). The scale was guessed
+ per value — four or more fractional-second digits meant nanoseconds, coarser
+ meant milliseconds — so one column could hold both scales six orders of
+ magnitude apart. A sub-millisecond document matched a `range` or `term` before
+ flush and vanished after it, because the millisecond bound bisected to nothing
+ against a nanosecond sort key. Precision is now a property of the field
+ (`date` is milliseconds, a declared `date_nanos` is nanoseconds), threaded
+ through every sort and shadow-range site. No on-disk format change.
+
+- **Numeric and boolean fields enforce their declared type**
+ ([#781](https://github.com/xerj-org/xerj/issues/781)). A field mapped
+ `integer` accepted `1.9` and kept it, accepted values outside the type's
+ range, and accepted non-numeric strings. Writes now follow ES's `coerce`
+ semantics: `1.9` into an integer type stores `1`, `"5"` stores `5`, and
+ out-of-range or unparseable values are refused with a 400 instead of being
+ stored. A field-level `"coerce": false` is honoured, and `ignore_malformed`
+ keeps precedence.
+
+ **Upgrade note:** coercion rewrites the value in `_source`, so an index that
+ spans this upgrade can hold both spellings of the same logical value. `term`
+ and `terms` on a boolean field now normalise their operand the way `term`
+ already did, and the two spellings compare equal, so a query matches
+ documents written on either side of the upgrade.
+
+- **`knn` beside `query` scores as a sum over the union**
+ ([#825](https://github.com/xerj-org/xerj/issues/825)). The ES-native hybrid
+ body silently dropped the vector half whenever aggregations, sort, collapse,
+ rescore or highlight were present: the request answered 200 with a purely
+ lexical result set and no warning. The vector leg is now pre-executed and its
+ top-k pinned into the query tree, so the hit set is the union, a document
+ reached by both halves scores the sum, and every request feature applies.
+
+ **Known regression, measured and not hidden:** on the hybrid shape that
+ previously took the RRF route, this is substantially slower — the pinned
+ clauses cannot project to the full-text index, so the query falls back to a
+ stored-document scan (~208 ms vs ~2.5 ms on a 100k-document index at k=10).
+ Correct-and-slow was chosen over fast-and-wrong;
+ [#892](https://github.com/xerj-org/xerj/issues/892) carries the indexed-route
+ design that removes it.
+
+- **`autoindex` never aborts a run over a legacy global-catalog mapping**
+ ([#755](https://github.com/xerj-org/xerj/issues/755)). Upgrading onto a
+ catalog whose `prefix` field pre-existed as `text` aborted the entire
+ indexing run. An upgrade must never do that.
+
+- **Removing a file no longer leaves graph edges pointing at it**
+ ([#736](https://github.com/xerj-org/xerj/issues/736)). Deletion removed a
+ file's documents and its outbound edges but left inbound edges dangling, so
+ graph queries returned edges to nodes that no longer existed.
+
+### Recorded late
+
+These shipped in rc.70 or earlier and were never written down, because
+rc.19–rc.70 have no CHANGELOG sections at all. They are recorded here rather
+than left under an "Unreleased" heading that misdescribes them; closing the
+rest of that gap is a GA item in [ROADMAP.md](./ROADMAP.md).
+
- **Wrapping a query in a one-clause `bool` no longer changes its `_score` or
its ranking** ([#399](https://github.com/xerj-org/xerj/issues/399)).
`{"bool":{"must":[X]}}` and bare `X` are the same query — Lucene's
diff --git a/ROADMAP.md b/ROADMAP.md
index bac4d2732..3b956ba9f 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -2,7 +2,7 @@
This roadmap tracks capabilities that are **planned but not yet fully implemented**, so the project's public claims stay honest about what ships today versus what is coming. Status is verified against the actual code and by real API requests to the release binary, not aspirational.
-Last reviewed: 2026-08-30 (against `v1.0.0-rc.71` and `main`). Statuses trace to issues, merged PRs, the CHANGELOG, and the conformance suite; items carried forward from the 2026-07-12 review without fresh live verification are marked as such. This review line is machine-checked: `docs_capability_lists` fails the build if a release is cut without re-reviewing this file (issue #298).
+Last reviewed: 2026-08-31 (against `v1.0.0-rc.72` and `main`). Statuses trace to issues, merged PRs, the CHANGELOG, and the conformance suite; items carried forward from the 2026-07-12 review without fresh live verification are marked as such. This review line is machine-checked: `docs_capability_lists` fails the build if a release is cut without re-reviewing this file (issue #298).
## Follow the roadmap
@@ -21,7 +21,7 @@ These are implemented and exercised by real API requests / the test suite / benc
- **Aggregations: <!-- generated:agg-type-count -->62<!-- /generated:agg-type-count --> types**, likewise generated from `xerj_engine::aggs::SUPPORTED_AGG_TYPES`, printed in [engine/README.md](./engine/README.md#aggregation-types-supported) and [llms-full.txt](https://xerj.org/llms-full.txt), and pinned by the same count test. This includes the full **pipeline family**. `weighted_avg` is **not** in `SUPPORTED_AGG_TYPES` — see *Known partials*.
**Exactness, precisely.** No probabilistic sketch sits in the metric path: `cardinality` is a true distinct count rather than an HLL estimate, and `terms` `doc_count` is precise. Two deliberate exceptions, stated the same way in `engine/README.md` and `llms-full.txt`: (1) the **sampling family** is a sample by definition — `run_sampler` sorts the matched documents by `_score` and keeps the first `shard_size` (default **200**), so every sub-aggregation under `sampler`, `random_sampler` or `diversified_sampler` is computed over that slice rather than the whole match set, `diversified_sampler` additionally caps documents per `field` value, and `random_sampler` shares the `sampler` implementation and **ignores ES's `probability`** (an accepted-and-ignored input, #204); (2) `percentiles` with the `hdr` option returns HdrHistogram-quantized values, deliberately, so ES's own outputs reproduce — the default `tdigest` path sorts every value and interpolates instead.
- **Dense-vector kNN** (`knn` query and ES 8.x top-level `knn`): unfiltered kNN on a full-precision cosine field (≥1,024 docs) is served by a **persisted HNSW graph with exact rescoring** — measured recall@10 1.00 on the official bench query, 100-probe mean 0.976 (ES 8.13.4 same protocol: 0.937); filtered/nested kNN, non-cosine similarity, SQ8 fields, and small indexes run the exact brute-force scan (cosine mapped to `(1+cos)/2`).
-- **Hybrid search** — BM25 + kNN combined in a single request via the `hybrid` **query type** with `rrf|linear` fusion, verified live. (`fusion: "learned"` is parsed and **rejected** with a 400 naming the supported values — it is not implemented.) (The ES-native top-level `{query, knn}` body does **not** fuse — see *Known partials*.)
+- **Hybrid search** — BM25 + kNN combined in a single request via the `hybrid` **query type** with `rrf|linear` fusion, verified live. (`fusion: "learned"` is parsed and **rejected** with a 400 naming the supported values — it is not implemented.) (The ES-native top-level `{query, knn}` body also unions both halves since rc.72 — see *Known partials* for its performance caveat.)
- **Zero-config folder onboarding** — `xerj autoindex <folder>` sniffs files, infers datasets, and creates one index per dataset: tree-sitter AST extraction for 34 languages (symbols, defs, line numbers — the [#295](https://github.com/xerj-org/xerj/issues/295) expansion; still open: Clojure and source-SQL wait on usable grammar crates, Nim/Crystal have none, fixed-form Fortran is deliberately unclaimed), CSV/JSON/JSONL/XML/YAML/SQLite/PDF/DOCX/HTML/log formats, `.gitignore`/`.xerjignore` support, incremental re-runs, and a machine-parseable progress stream.
- **Agent-memory REST API** (`/_memory/*`), **second-brain knowledge graph** (`/_graph`), **anomaly detection** (`_ml` with continuous datafeeds), **auto-embed on ingest** (default embedder is deterministic **lexical** feature-hashing — never described as neural; `--embed-mode neural` runs the in-binary BERT encoder, `--embed-mode proxy` an external endpoint).
- **Columnar storage** — the ZBS2 columnar block with 9 domain-aware encodings, ZSTD/LZ4 codecs, and SQ8 vector quantization, wired into the segment write path.
@@ -30,44 +30,45 @@ These are implemented and exercised by real API requests / the test suite / benc
The release-by-release record of how all of this landed is [CHANGELOG.md](./CHANGELOG.md) — this file no longer duplicates it. Be aware of a real gap in that record: rc.1–rc.18 and rc.71 have entries, **rc.19 through rc.70 do not**. Those 52 releases are reconstructable only from `git log` and the release list, and closing that gap is itself a GA item below.
-## Next release — [v1.0.0-rc.72](https://github.com/xerj-org/xerj/milestones)
-
-rc.71 was cut on 2026-08-29 — its full contents are the [CHANGELOG.md](./CHANGELOG.md)
-entry, not this file. It is an Elasticsearch-compatibility correctness release: 30 query,
-aggregation and API semantics fixes, a ~100x incremental re-index
-([#868](https://github.com/xerj-org/xerj/pull/868)), and two metrics counters that had been
-registered but never incremented ([#804](https://github.com/xerj-org/xerj/issues/804),
-[#819](https://github.com/xerj-org/xerj/issues/819)).
-
-**In flight for rc.72**, all opened against measured evidence rather than intuition:
-
-- **Idle resource cost** — a 2026-08-29 measurement session found that on a node holding many
- small indices (what `xerj autoindex` produces from a reference corpus) the process is not
- quiet at rest: 464 idle indices cost 15–27% of a core and 115 wakeups/s. Three mechanisms,
- each located at `file:line` and budgeted in public under the
- [#874](https://github.com/xerj-org/xerj/issues/874) meta-issue: the per-index 5-second merge
- tick ([#871](https://github.com/xerj-org/xerj/issues/871)), a sampler walking every index ×
- every shard lock at 10 Hz ([#872](https://github.com/xerj-org/xerj/issues/872)), and a
- per-index resident floor ([#873](https://github.com/xerj-org/xerj/issues/873)). The budget
- the fixes are held to: idle CPU under 0.5% of one core *independent of index count*.
-- **Merge re-analyzes documents instead of merging postings**
- ([#876](https://github.com/xerj-org/xerj/issues/876)) — the post-ingest merge tail ran 40+
- minutes at ~110% CPU on a 154 MB corpus and drove RSS into the write breaker. The segment
- writer already accepts a `PostingsWriter` rather than text, so the fix reuses machinery that
- exists rather than adding any.
-- **Multi-index search fan-out was serial**
- ([#875](https://github.com/xerj-org/xerj/issues/875)) — an `ax-*` search cost the sum of its
- per-index latencies instead of the maximum. This matters most for reference-coding, whose
- documented retrieval queries `ax-*`.
-- **ES-compatibility semantics** — `knn` beside `query` silently dropping the vector half
- ([#825](https://github.com/xerj-org/xerj/issues/825)), `match_phrase` slop rejecting
- transpositions Lucene accepts ([#830](https://github.com/xerj-org/xerj/issues/830)),
- sub-millisecond date bounds after flush ([#790](https://github.com/xerj-org/xerj/issues/790)),
- and numeric/boolean fields not enforcing their declared type
- ([#781](https://github.com/xerj-org/xerj/issues/781)).
-- **CI reliability** — [#751](https://github.com/xerj-org/xerj/issues/751), an intermittent hang
- in the default-parallelism workspace test step, still bounded rather than fixed. A flaky gate
- is a gate nobody trusts, and it stays on this list until the race is found.
+## Next release — [v1.0.0-rc.73](https://github.com/xerj-org/xerj/milestones)
+
+rc.72 was cut on 2026-08-31 — its full contents are the [CHANGELOG.md](./CHANGELOG.md)
+entry, not this file. It is **the idle-cost release**: a measurement session found the
+process was not quiet at rest — 464 small indices (the shape `xerj autoindex` produces)
+cost 15-27% of a core and 115 wakeups/s with zero requests, and a 154 MB corpus spent
+40+ minutes at ~110% CPU merging after ingest "finished". Three of the four mechanisms
+are fixed ([#871](https://github.com/xerj-org/xerj/issues/871) event-driven merge
+scheduling, [#872](https://github.com/xerj-org/xerj/issues/872) an incremental memtable
+aggregate replacing 74,240 lock acquisitions per second,
+[#873](https://github.com/xerj-org/xerj/issues/873) an idle-age flush so a small dataset
+reaches a segment instead of living in RAM). It also carries six ES-compatibility and
+autoindex correctness fixes, each with a test proven to fail on the unfixed code.
+
+**In flight for rc.73:**
+
+- **The fourth idle-cost mechanism** — merge re-analyzes every document instead of
+ merging postings ([#876](https://github.com/xerj-org/xerj/issues/876)). The segment
+ writer already accepts a `PostingsWriter` rather than text, so the fix reuses machinery
+ that exists; the design is published on the issue. The
+ [#874](https://github.com/xerj-org/xerj/issues/874) budget — idle CPU under 0.5% of one
+ core *independent of index count* — is not met until this and the remaining
+ [#873](https://github.com/xerj-org/xerj/issues/873) levers (adaptive WAL shards,
+ cold-index state) land.
+- **The regression rc.72 shipped knowingly** — `knn` beside `query` is now correct but is
+ answered by a stored-document scan ([#892](https://github.com/xerj-org/xerj/issues/892)).
+- **Retrieval quality** — the symbol index returns whole class and method bodies rather
+ than declarations, measured at 32-48x more bytes than grep for the same answer
+ ([#500](https://github.com/xerj-org/xerj/issues/500)). This one undercuts a claim the
+ project leads with, so it is a correctness issue about our own marketing as much as a
+ performance one.
+- **CI reliability** — [#751](https://github.com/xerj-org/xerj/issues/751) still hangs the
+ default-parallelism test step intermittently, and it was red on `main` repeatedly during
+ the rc.72 cut. The cost is not the failed run, it is that a red gate stops distinguishing
+ a real break from noise. [#891](https://github.com/xerj-org/xerj/issues/891) is a
+ confirmed instance of the same class (a process-global counter two tests share).
+- **Data-loss follow-up** — [#890](https://github.com/xerj-org/xerj/issues/890): the
+ prefix-scoped exclusion sweep can over-delete across corpora on a legacy text-mapped
+ catalog. Filed against code that shipped in rc.72.
## The road to [v1.0.0 GA](https://github.com/xerj-org/xerj/milestone/2)
@@ -105,7 +106,7 @@ Carried forward from the 2026-07-12 review, not re-verified live since:
- **`span_term` / `span_or` / `span_not`** — return 0 hits **standalone**, while composite span queries (`span_near` / `span_first` / `span_containing`) using the same clauses return correct hits.
- **`type`** — mapped to `MatchAll`.
- **`combined_fields`** — mapped to `multi_match cross_fields`; scoring is not exact. `rank_feature` passes through on plain fields (no `rank_feature` field type).
-- **ES-native top-level `{query, knn}`** — does not union the kNN hits; one-request BM25+kNN fusion works only through the explicit `hybrid` query type. **Fix open as [#879](https://github.com/xerj-org/xerj/pull/879)** ([#825](https://github.com/xerj-org/xerj/issues/825)): it pre-executes the vector leg and pins its top-k so the union scores as ES's documented sum. This line stays until that merges — a roadmap describes what ships, not what is in review.
+- **ES-native top-level `{query, knn}` — RETIRED in rc.72.** It now unions both halves and scores a document reached by both as the sum, aggregations included ([#825](https://github.com/xerj-org/xerj/issues/825) via [#879](https://github.com/xerj-org/xerj/pull/879)). It is kept in this list for one release with its replacement caveat, which is a performance one rather than a correctness one: the pinned clauses cannot project to the full-text index, so this shape is answered by a stored-document scan and is substantially slower than the `hybrid` query type (~208 ms vs ~2.5 ms measured on 100k documents at k=10). [#892](https://github.com/xerj-org/xerj/issues/892) carries the indexed-route fix. Correct-and-slow was chosen deliberately over fast-and-wrong.
---
diff --git a/engine/Cargo.lock b/engine/Cargo.lock
index 6e6808fd1..62de03471 100644
--- a/engine/Cargo.lock
+++ b/engine/Cargo.lock
@@ -6619,7 +6619,7 @@ dependencies = [
[[package]]
name = "xerj-ai"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"candle-core",
@@ -6640,7 +6640,7 @@ dependencies = [
[[package]]
name = "xerj-api"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"async-trait",
@@ -6671,7 +6671,7 @@ dependencies = [
[[package]]
name = "xerj-autoindex"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"chrono",
@@ -6736,7 +6736,7 @@ dependencies = [
[[package]]
name = "xerj-cluster"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"async-trait",
@@ -6761,7 +6761,7 @@ dependencies = [
[[package]]
name = "xerj-common"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"byteorder",
@@ -6780,7 +6780,7 @@ dependencies = [
[[package]]
name = "xerj-compress"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"byteorder",
"bytes",
@@ -6793,7 +6793,7 @@ dependencies = [
[[package]]
name = "xerj-console-api"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"arc-swap",
@@ -6829,7 +6829,7 @@ dependencies = [
[[package]]
name = "xerj-engine"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"arc-swap",
@@ -6883,7 +6883,7 @@ dependencies = [
[[package]]
name = "xerj-fts"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"bitpacking",
@@ -6910,7 +6910,7 @@ dependencies = [
[[package]]
name = "xerj-logs"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"byteorder",
@@ -6928,7 +6928,7 @@ dependencies = [
[[package]]
name = "xerj-mcp"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"reqwest",
@@ -6939,7 +6939,7 @@ dependencies = [
[[package]]
name = "xerj-query"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"base64 0.22.1",
@@ -6954,7 +6954,7 @@ dependencies = [
[[package]]
name = "xerj-server"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"axum",
@@ -7002,7 +7002,7 @@ dependencies = [
[[package]]
name = "xerj-storage"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"arc-swap",
@@ -7032,7 +7032,7 @@ dependencies = [
[[package]]
name = "xerj-vector"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"byteorder",
@@ -7050,7 +7050,7 @@ dependencies = [
[[package]]
name = "xerj-wasm"
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
dependencies = [
"anyhow",
"bytes",
diff --git a/engine/Cargo.toml b/engine/Cargo.toml
index 7c87a345d..e56082f3f 100644
--- a/engine/Cargo.toml
+++ b/engine/Cargo.toml
@@ -21,7 +21,7 @@ members = [
]
[workspace.package]
-version = "1.0.0-rc.71"
+version = "1.0.0-rc.72"
edition = "2021"
license = "Apache-2.0"
authors = ["xerj Contributors"]