narrowdb 0.3.2

A lightweight columnar database engine for log and time-series data
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

# Release Guide

This repository ships three public distribution surfaces:

- Rust crate: `narrowdb`
- Docker image for `narrowdb-server`
- npm package: `@narrowdb/node`

## Before tagging

1. Update versions together:
   - [Cargo.toml](../Cargo.toml)
   - [crates/server/Cargo.toml](../crates/server/Cargo.toml)
   - [crates/narrow-napi/Cargo.toml](../crates/narrow-napi/Cargo.toml)
   - [crates/narrow-napi/package.json](../crates/narrow-napi/package.json)
2. Add a matching changelog section in [CHANGELOG.md](./CHANGELOG.md).
3. Run:

```bash
./tools/release/check-release.sh
cargo fmt --all --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
```

## Tagging

Create and push a version tag in the form `vX.Y.Z`.

Example:

```bash
git tag v0.3.1
git push origin v0.3.1
```

Tag pushes trigger:

- Docker publish workflow
- npm publish workflow

## Artifact expectations

- Docker image tags:
  - `ghcr.io/lassejlv/narrowdb:vX.Y.Z`
  - `ghcr.io/lassejlv/narrowdb:latest`
- npm package:
  - `@narrowdb/node@X.Y.Z`

## Notes

- Rust crate publishing is still a separate explicit step if you want crates.io publication.
- npm publication assumes the N-API artifacts build successfully for all configured targets.
- MD5 auth on the server should be treated as trusted-network only until stronger auth lands.