v0.4.2
Highlights
The engine crate is now named seance. The binary, the GitHub
release asset, the wasm package, and the docker image are all
seance. The product on the website stays Necrometer — the
"seance" is the act of communing with your dead repos.
What's in this release
Renamed:
- Crate
necrometer→seance(Cargo.toml[package].name,
[lib].name,[[bin]].name). - CLI binary
necrometer→seance—./seance card torvalds necrometer.svg. - GitHub release asset
necrometer-x86_64-unknown-linux-musl.tar.gz
→seance-x86_64-unknown-linux-musl.tar.gz. - wasm-pack package name
necrometer→seance(.wasm-pack.toml). - Wasm artifacts
pkg/necrometer.js+pkg/necrometer_bg.wasm+
pkg/necrometer.d.ts+pkg/necrometer_bg.wasm.d.ts→
pkg/seance.js+pkg/seance_bg.wasm+pkg/seance.d.ts+
pkg/seance_bg.wasm.d.ts. - CLI usage strings:
seance serve | seance card <name> [out.svg] | seance hall <names> [out.json].
Kept (intentional):
- The product name on
necrometer.devstaysNecrometer. - The GitHub org/repo names stay
necrometer-dev/...— those are
not renamed. - The action (
necrometer-dev/necrometer-action) keeps its name —
consumers depend onuses: necrometer-dev/necrometer-action@v1. - The card output file stays
necrometer.svg— that's what
README badges link to.
Required consumer changes:
- Workflows calling the action: no change — the action now points
atv0.4.2by default and downloadsseance-*.tar.gz
automatically. - Sites embedding the wasm: update import paths
import init from './pkg/seance.js',
await init('./pkg/seance_bg.wasm'). - Anyone consuming the release artifact directly: switch to
seance-x86_64-unknown-linux-musl.tar.gz.
Internal cleanups
src/time.rs:SystemTimeimport is#[cfg(not(target_arch = "wasm32"))]— wasm builds cleanly without it..wasm-pack.toml: new file documenting the wasm-pack package name
(was previously implicit inwasm-pack builddefaults).
Verification
cargo test --lib → 47 passed
cargo clippy ... -- -D warnings → clean
cargo fmt --all -- --check → clean
cargo build --bin seance → ok
cargo build --bin seance --features serve → ok
cargo build --lib --target wasm32-unknown-unknown → ok
wasm-pack build --release --target web ... → ok
node smoke test → reading=354 svg=44590