Repository navigation
@harperfast/fulltext v0.8.0
Published to npm: @harperfast/fulltext 0.8.0 and all four matching native packages are available; latest points to 0.8.0.
Release correction: before any npm publication, Kyle approved moving v0.8.0 from the initial release commit to the supported-runner repair. Only two macOS runner labels changed; application sources are identical. The initial packaging attempt encountered GitHub's macOS 14 brownout. Original benchmark assets were preserved before restarting.
Compatibility: rebuild existing string-metadata indexes
Indexes with string filterFields need rebuilding when upgrading from 0.7.0. Version 0.8.0 adds raw fast fields for metadata sorting and aggregations. Incompatible indexes fail closed with E_IDENTITY_MISMATCH; do not edit identity sidecars to bypass the check.
Drain work and close every reader and writer, retire the old index with resetNativeFullTextIndex(), and rebuild from authoritative records using a new generation. Publish source-checkpoint coverage only after rebuilding, then verify reopen, filters, sorting and aggregations before cutover. Numeric/Boolean-only indexes retain compatibility when the rest of their configuration is unchanged. Always deploy matching JavaScript and native package versions.
See the metadata migration guide for upgrade, downgrade and recovery procedures. Earlier analyzer migration requirements still apply to upgrades from 0.6.x.
What changed
- Global multi-field metadata sorting, native nested aggregations and additional filter predicates: Add global metadata sorting, facets, and filter predicates.
- Per-handle analyzed-term and compiled-clause capacity, with shared structural admission: Make analyzed query capacity configurable per handle.
- Fuzzy edit-distance and transposition controls, native exact matching at distance zero, and aligned request validation: Expose fuzzy matching controls and align Rust request validation.
- Aligned release versions, stronger worker-fixture cleanup and test-only Windows diagnostics: Prepare fulltext 0.8.0 for release.
Tantivy remains 0.27.0. Distance-two fuzzy matching remains preview with no hard process-memory bound; qualify corpus and concurrency before exposing it to callers. Deadlines remain cooperative. Phrase slop is deferred; no unreleased Tantivy patch is included.
Verification and remaining uncertainty
The repaired release commit passed all 17 main CI jobs across Linux x64/arm64, macOS arm64 and Windows x64, including Node 22.18, 24 and 26. The publish workflow built all four native packages and the JavaScript facade, passed packed-consumer installs and public examples on all four platforms, and published all five packages with provenance.
Public registry checks verified every 0.8.0 package and the root latest dist-tag. A separate clean npm installation on macOS ARM64 reports wrapper 0.8.0 / Tantivy 0.27.0, with all nine shipped examples passing. The release benchmark workflow passed, and all eight Linux benchmark result files are attached.
Historical Windows stalls and sustained-memory qualification remain tracked in Qualify remaining native metadata collector resource tradeoffs. Passing CI does not establish their cause or production memory headroom.
Comment generated by kAIle (GPT-6)