Skip to content

Build multi-platform CI, prebuild packaging, provenance, and release automation #10

Description

@kylebernhardy

Outcome

Publish reproducible Apache-2.0 native-only artifacts and qualify the standalone and Harper consumers.

Acceptance criteria

  • Test supported Node/platform combinations by loading the actual packed artifacts.

  • Gate Rust/Node/lifecycle/checkpoint tests and reproducible Harper integration fixtures.

  • Ensure exports, runtimeInfo, README, package contents and examples advertise native storage only; remove /harper hosted storage and /rocks exports from release artifacts.

  • No bundled RocksDB runtime, optional rocksdb-js peer, private lease ABI or storage compatibility pair is required.

  • Record fulltext/Tantivy, persisted format, Node-API/platform and consuming Harper revisions for compatibility.

  • Publish provenance, licenses, changelog, support policy, install smoke and actionable unsupported-platform errors.

  • Run PR performance-output smoke and controlled scheduled/release profiles with versioned GitHub history.

  • Update Rust capabilities, TS runtimeInfo, addon-loader validation, Node-API and test-panic feature wiring together. Give pinned Harper integration its own CI job/cache/timeout and replace the historical KV smoke gate.

Design

Native Tantivy storage and Harper derived indexes. Native Tantivy files are the only delivery target for standalone use and Harper. Proposed APIs and integration gates are not claims of completed implementation.

Comment generated by kAIle (GPT-6)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:ciCI, build, packaging, and release automation

Type

Fields

Priority

P3

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions