Release the ABI 17 / query API 10 build under a new version (Boolean and recoverable tracing)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- nodejs, rust, typescript
- Área
- release
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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)
- Lenguaje dominante
- Rust
- Estrellas
- 3
- Forks
- 0
- Merge medio
- 20 h 29 min
- PR fusionados (30 d)
- 13
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de HarperFast/fulltext
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
HarperFast/fulltext#91 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 18/100
HarperFast/fulltext#89 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 18/100
HarperFast/fulltext#88 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
HarperFast/fulltext#76 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
HarperFast/fulltext#74 ·
Los mantenedores suelen responder en 1 día
Todos los issues de HarperFast/fulltext
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
DioxusLabs/blitz#1614 ·
Los mantenedores suelen responder en 1 día
-
ms lint --fix removes the Decimal import that a decimal literal needs, then re-adds it foreverAbiertoin progress
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
manuscript-lang/manuscript#4385 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
boxlite-ai/boxlite#2777 ·
Los mantenedores suelen responder en 1 día
-
custom-types postgres
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
tursodatabase/turso#11908 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
buckyos/buckyos#741 · 1 comentario ·
Los mantenedores suelen responder en 1 día