release-core-test

Files (1)

• SKILL.md

SKILL.md (first lines)

# Release Core (Test)

Publish ONLY the `miko-core` package (and `claude-runner` if needed) as a dev/test prerelease to npm under the `test` dist-tag. This is a developer convenience for iterating on `miko-core` without going through the full release flow.

## What this skill does NOT do

This skill is intentionally minimal. It does **NOT**:

- Update `CHANGELOG.md` or `CHANGELOG.internal.md`
- Create a git tag
- Create a GitHub release
- Move any Linear issues
- Open a pull request
- Commit the version bump (the bumped `package.json` is left as a local working-tree change)

It also does NOT publish any other workspace package (no `edge-worker`, no `miko` CLI, no `linear-event-transport`, etc.). The only exception is `claude-runner`, which is republished if and only if its `workspace:*` reference would otherwise resolve to an unpublished version (see step 3 below).

## Workflow

### 1. Install dependencies from repo root

```bash
pnpm install
```

### 2. Build all packages from repo root

```bash
pnpm build
```

Building all packages ensures `workspace:*` dependencies are resolved before publishing.

### 3. Determine whether `claude-runner` needs republishing

`miko-core` depends on `claude-runner` via `workspace:*`. When `miko-core` is published, that `workspace:*` is rewritten to the version currently in `packages/claude-runner/package.json`. If that version isn't actually on npm yet (because `claude-runner` has local changes since its last publish), consumers installing `miko-core@test` will fail to resolve the dependency.

Run both of these deterministic checks:

```bash
# (a) Is the local claude-runner version already on npm?
LOCAL_CR=$(node -p "require('./packages/claude-runner/package.json').version")
npm view "miko-claude-runner@${LOCAL_CR}" version 2>/dev/null

# (b) Does claude-runner have uncommitted/unpushed source changes since its last publish?
git diff --quiet HEAD -- packages/claude-runner/src packages/claude-runner/package.json && echo "clean" || echo "dirty"
```

Republish `claude-runner` if **either**: (a) returns nothing (local version is not on npm), **or** (b) prints `dirty`. If both pass cleanly, skip this step. If you're unsure, ask the user.

To republish:

```bash
# Determine the next -test.N for claude-runner (same algorithm as miko-core below)
# Bump packages/claude-runner/package.json to e.g. 0.0.X-test.N
cd packages/claude-runner
pnpm publish --access public --no-git-checks --tag test
cd ../..
pnpm install   # refresh lockfile so miko-core picks up the new claude-runner
```

Otherwise, skip this step entirely.

### 4. Bump `miko-core` to the next `-test.N` prerelease version

Algorithm:

1. Read the current version from `packages/core/package.json` (e.g. `0.1.22`).
2. Bump the patch (e.g. `0.1.23`).
3. Append `-test.N`, starting at `N = 0` and incrementing while `<bumped>-test.N` already exists on npm (including aborted/stale prior attempts).

Use this one-liner to find existing `-test.N` versions for the bumped patch and pick the next N:

```bash
BUMPED=0.1.23   # the patch-bumped base, no suffix
npm view miko-core versions --json \
  | jq -r '.[]' \
  | grep -E "^${BUMPED}-test\.[0-9]+$" \
  | awk -F'test.' '{print $2}' \
  | sort -n | tail -1
# If empty, use N=0. Otherwise use (max + 1).
```

Write the chosen version (e.g. `0.1.23-test.0`) back into `packages/core/package.json`. Do NOT commit this change — leave it as a local working-tree edit so the developer can decide whether to keep it.

### 5. Publish `miko-core` with the `test` dist-tag

```bash
cd packages/core
pnpm publish --access public --no-git-checks --tag test
cd ../..
```

Using `--tag test` means:

- `npm install miko-core@test` will install this version.
- The `latest` dist-tag is **not** moved, so production installs (`npm install miko-core`) are unaffected.

### 6. Verify the dist-tags landed correctly

```bash
npm view miko-core dist-tags
```

Confirm that `latest` is unchanged from before the publish and `test` now points to the version you just published. If `latest` moved, something is wrong — stop and investigate before telling anyone to install it.

### 7. Print install instructions

After publishing, print both forms so the developer can copy/paste:

```
Published miko-core@<version> under dist-tag `test`.

Install with:
  npm install miko-core@test
or pinned:
  npm install miko-core@<version>
```

From mikoagents/miko, Apache-2.0.

More from mikoagents/miko