Tags: loopworx/loopkit

fix: properly extract tarball in npm postinstall (was gunzipping, not…

… untarring)

ENOEXEC error was caused by writing the tar archive as the binary instead of extracting it.
Now downloads to temp dir, extracts with tar/7z, then moves binary to bin/.

release v0.3.2

fix: add README to crates.io and npm packages; bump to v0.3.1

- Copy root README.md to each crate directory and npm/
- Add readme = 'README.md' to all Cargo.toml manifests
- Add README.md to npm files array
- Fix cross_references test: return early on empty skills
- Bump version 0.3.0 -> 0.3.1 (0.3.0 already published)

fix: use loopkit-cli npm name; idempotent crates.io publish

- npm name 'loopkit' taken, '@loopworx' scope not created, use 'loopkit-cli'
- crates.io: continue-on-error so re-runs skip already-published crates