Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.
2026-08-01 15:44:40 -07:00

3.0 KiB

Releases

Releases are prepared with Sampo changesets and published by the Release CLI workflow's cargo-dist jobs.

When making a releasable CLI change, add a changeset from the ./cli directory:

sampo add --package cargo/insights-cli --bump patch --message "Describe the CLI change"

Use minor or major instead of patch when appropriate. Commit the generated file under cli/.sampo/changesets/ with your pull request.

After the pull request merges to master, the Release CLI workflow:

  1. Checks for pending CLI changesets
  2. Waits for approval in the GitHub Release SDK environment
  3. Runs sampo release from ./cli
  4. Updates cli/Cargo.toml, cli/Cargo.lock, and cli/CHANGELOG.md
  5. Commits the release bump to master
  6. Runs cargo-dist against the release bump commit
  7. Creates the insights-cli/vX.Y.Z GitHub release, refreshes insights-cli-latest for stable releases, and publishes the npm package

Do not run sampo publish; cargo-dist owns publishing for insights-cli.

If you need to cut a release by hand, merge a CLI changeset to master and let Release CLI run from there. Do not push insights-cli/vX.Y.Z tags manually; cargo-dist tag-push releases are disabled. If cargo-dist fails after Release CLI commits the release bump, rerun the failed jobs from the same workflow run.

The release workflow also builds services/mcp into cli/lib/insights-api-cli.mjs before cargo-dist packages artifacts. This keeps insights-cli api aligned with the generated MCP tool catalog at release time. To reproduce that release bundle locally, run:

pnpm --dir services/mcp run build:cli:release

To smoke-test the packaged CLI before cutting a release, build the same cargo-dist archive and installer locally, then run both the unpacked archive and the generated shell installer from a temporary home directory:

flox activate -- bash -c 'cargo install cargo-dist --version 0.32.0 --locked'
DIST_BIN="$HOME/.cargo/bin/dist" flox activate -- bash -c './cli/scripts/smoke-release-artifact.sh'

If you are testing uncommitted local changes, set CLI_RELEASE_SMOKE_ALLOW_DIRTY=1 for the second command. The smoke test verifies that the archive includes lib/insights-api-cli.mjs, that insights-cli api --agent-help works from the unpacked artifact, and that the generated shell installer produces a working insights-cli api install without relying on a Insights repo checkout. It serves target/distrib on 127.0.0.1:8765 while testing the installer; set CLI_RELEASE_SMOKE_PORT if that port is already in use. It does not replace any insights-cli already on your PATH; to manually test the built artifact, run target/distrib/insights-cli-$(rustc -vV | sed -n 's/^host: //p')/insights-cli api --agent-help.

We release semi-regularly, as new features are added. If a release breaks your CI or workflow, please open an issue on GitHub, and tag one or all of the crate authors