Skip to content

release: v0.8.2 — npm under @kimetsu-ai scope#12

Merged
RodCor merged 1 commit into
mainfrom
release/v0.8.2
Jun 1, 2026
Merged

release: v0.8.2 — npm under @kimetsu-ai scope#12
RodCor merged 1 commit into
mainfrom
release/v0.8.2

Conversation

@RodCor

@RodCor RodCor commented Jun 1, 2026

Copy link
Copy Markdown
Owner

Re-cuts the npm channel under the available names and ships v0.8.2.

Why

kimetsu (npm) and @kimetsu (scope) were unavailable. The npm org is kimetsu-ai.

Naming

  • Main package: kimetsu-ai (unscoped) → npm install -g kimetsu-ai
  • Platform packages: @kimetsu-ai/{linux-x64,darwin-x64,darwin-arm64,win32-x64}
  • Installs both kimetsu and kimetsu-ai commands.

Changes

  • Launcher PLATFORMS map, optionalDependencies, publish-npm job generation + summary, and all docs rewired @kimetsu/*@kimetsu-ai/*, kimetsukimetsu-ai.
  • Workspace bumped 0.8.1 → 0.8.2 (Cargo.toml, Cargo.lock). v0.8.1 shipped crates + binaries; npm first ships in 0.8.2.

Verified

  • Launcher resolves @kimetsu-ai scope + execs the real binary; npm pack clean (4 files, no binary); cargo check --locked green at 0.8.2.

🤖 Generated with Claude Code

The `kimetsu` npm name and `@kimetsu` scope were unavailable, so the npm
channel ships as the unscoped `kimetsu-ai` package with per-platform
binaries under the `@kimetsu-ai` scope. Rewire the launcher map,
optionalDependencies, the publish-npm CI job, and docs accordingly, and
bump the workspace to 0.8.2 (v0.8.1 shipped crates + binaries; npm first
ships here). The package installs both `kimetsu` and `kimetsu-ai` commands.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@RodCor
RodCor merged commit 522f184 into main Jun 1, 2026
5 of 8 checks passed
@RodCor
RodCor deleted the release/v0.8.2 branch June 1, 2026 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant