Release the ABI 17 / query API 10 build under a new version (Boolean and recoverable tracing)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- nodejs, rust, typescript
- Ambito
- release
Direzione di ricerca
Start with the version constants in src/lib.rs (ABI 17 at line 32, query API 10 at line 92) and the version fields in package.json and Cargo.toml, then read docs/limits.md lines 516-518 for the rule on choosing an unused release version. The version check in ts/load-addon.ts around line 89 explains why the two 0.9.0 builds collide. Done means every manifest and lockfile carries the new version, the README has an upgrade section for 0.9.x, and the release is published; the version choice itself needs a maintainer decision first.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
main is four commits past the v0.9.0 tag and has a different native contract, but package.json and Cargo.toml still say 0.9.0. Nothing tracks cutting the release, and two merged features and two Harper issues are waiting on it.
| Published 0.9.0 | main (d94fc36) |
|
|---|---|---|
| Native ABI | 14 | 17 (src/lib.rs:32) |
| Query API | 8 | 10 (src/lib.rs:92) |
| Package version | 0.9.0 | 0.9.0 (package.json:3) |
docs/limits.md:516-518 already says: "Development version 0.9.0 is not permission to replace published 0.9.0... Choose an unused synchronized release version before publication."
What the release carries
- Support Boolean expressions in source match tracing and snippets #84, for Support Boolean search expressions in match tracing and snippets #59
- Expose recoverable source match tracing with per-record completeness #85, for Expose trace progress and per-record truncation for bounded highlight recovery #68
What waits on it
- Adopt Boolean-aware full-text highlights and snippets #3965
- Adopt recoverable full-text highlighting with per-record completeness #4016. Harper currently fails a whole highlighted page with a 500 when one record exceeds the trace span cap, so this one has a user-visible cost.
- Harper has to relax its exact-equality version pins before it can load the new release: Full-text binding validation pins the library ABI and query API by exact equality, blocking the next fulltext release #4381.
Checklist
- Pick an unused version and align root, Cargo and platform manifests, exact optional dependencies and lockfiles.
- Consider bumping the packed protocol version too. It stayed at 8 while expression kinds 4/5 and the Boolean trace frames were added, so the ABI constant is currently the only gate for those layouts.
- Add a README "Upgrading from 0.9.x" section. The stricter trace-request validation from Support Boolean expressions in source match tracing and snippets #84 is described as a compatibility change in Support Boolean search expressions in match tracing and snippets #59 but has no upgrade note.
- Publish, then close Support Boolean search expressions in match tracing and snippets #59 and Expose trace progress and per-record truncation for bounded highlight recovery #68.
Risk until then: a facade built from main resolves npm's 0.9.0 platform binaries and fails with E_NATIVE_ABI_MISMATCH, because the loader's package-version check cannot tell the two 0.9.0s apart (ts/load-addon.ts:89).
Issue generated by kAIle (Claude Fable 5.2)
- Lingua principale
- Rust
- Stelle
- 3
- Fork
- 0
- Merge medio
- 20h 29m
- PR unite (30g)
- 13
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di HarperFast/fulltext
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
HarperFast/fulltext#91 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 18/100
HarperFast/fulltext#89 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 18/100
HarperFast/fulltext#88 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
HarperFast/fulltext#76 · 5 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
HarperFast/fulltext#74 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di HarperFast/fulltext
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
DioxusLabs/blitz#1614 ·
I maintainer di solito rispondono entro 1 giorno
-
ms lint --fix removes the Decimal import that a decimal literal needs, then re-adds it foreverApertain progress
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
manuscript-lang/manuscript#4385 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
boxlite-ai/boxlite#2777 ·
I maintainer di solito rispondono entro 1 giorno
-
custom-types postgres
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
tursodatabase/turso#11908 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
buckyos/buckyos#741 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno