Release the ABI 17 / query API 10 build under a new version (Boolean and recoverable tracing)

Abierto
#90 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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

What waits on it

Checklist

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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HarperFast/fulltext

Todos los issues de HarperFast/fulltext

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.