release

name	release
description	Release a new version of loopbase to npm end-to-end: bump the version, publish the scoped package, record the bump via PR, and update the local global install. Use when asked to "publish loopbase", "release loopbase", "cut a release", "ship a new version to npm", "publish to npm", or after merging fixes you want live on npm.

Releasing loopbase

Package: @superdesign/loopbase (scoped — the bare loopbase name is blocked by npm as "too similar to loopback"). Installed bins stay loopbase/lb. Source is published (no build step); npm publish packs the files whitelist from the working tree, so always publish from a clean checkout.

Preconditions

• All fixes for this release are merged into main (publish from main, not a dirty tree or a feature branch).
• Pick the new version: patch for fixes, minor for features. Versions are immutable — you can't republish or cleanly unpublish, so bump every time. Current published: npm view @superdesign/loopbase version.

Steps

1. Publish from a clean checkout of main (isolated worktree → never ships a dirty tree or another session's WIP):

   git fetch origin
   git worktree add -b release/x.y.z /tmp/lb-pub origin/main
   cd /tmp/lb-pub
   npm version x.y.z --no-git-tag-version    # bumps package.json only (no git tag)
   npm publish --dry-run                      # sanity: name, version, file count
   

2. Auth + OTP. The npm account has 2FA, and the token expires between releases.