| name | malloy-update |
| description | Bump @malloydata/* to the latest published version and ship it end to end — fresh main → worktree → npm run malloy-update → preflight → PR → wait green → merge → wait for the release action → report the new @malloydata/malloyyo version → clean up. Use when the user wants to pull a new Malloy npm release into this repo (e.g. "/malloy-update", "update malloy", "pull the new malloy"). |
malloy-update
Drive a Malloy npm bump from a clean main all the way to a published release of
this repo's CLI (@malloydata/malloyyo). Run from the primary ~/yo checkout.
This is a long, mostly-unattended pipeline with real stop conditions. Work the
steps in order, stop the moment a stop condition fires, and report what
happened. Don't invent fallbacks — if something is red, surface it and halt.
The two versions in play
primary — the @malloydata/malloy version being pulled in. It names the
branch, the PR, and the "in" side of the report. Call it $V.self — this repo's own @malloydata/malloyyo (the CLI) version. The
release patch-bumps and publishes it; it's the "out" side of the report.
The update script reports both in its JSON, so you never have to read a
manifest or guess a version — capture them from the tool.
Tools you'll lean on
npm run --silent malloy-update -- --json — drive the bump; emits, on stdout,
{ "primary", "self", "changed": bool, "packages": [{name, from, to}] }.
Add --dry-run to peek (network, no write) or --current to read just what's
installed now (offline, instant: { "primary", "self", packages:[{name,version}] }).
Human chatter and npm output always go to stderr.npm run preflight → bash scripts/preflight.sh — the offline gate
(typecheck + unit + cli build + server lint + next build + hosted-explore
integration test). Needs a running Docker daemon; if Docker is down the
hosted test fails — tell the user rather than papering over it.gh for the PR (gh pr create, gh pr checks --watch, gh pr merge) and the
release run (gh run list/watch --workflow=cli-publish.yml). Assume it's authed.
Long blocking steps (preflight, gh ... --watch, gh run watch) are best run as
background commands so you get a completion notification instead of polling.
Steps
1. Preconditions on main — STOP if violated
git -C ~/yo rev-parse --abbrev-ref HEAD
git -C ~/yo status --porcelain
git -C ~/yo fetch origin
git -C ~/yo pull --ff-only origin main
STOP and report if: not on main, the tree is dirty, or the pull isn't a clean
fast-forward. Don't stash or force anything.
2. Peek the target — STOP if not new
npm run --silent malloy-update -- --dry-run --json > /tmp/malloy-update.json
cat /tmp/malloy-update.json
(stdout → file is the clean JSON; stderr stays on screen so you still see the
per-package report and any error.) From the JSON, record:
changed — if false, STOP: report "@malloydata/* already at the latest
(primary) — nothing to do." No worktree, no PR.$V = primary — the Malloy version; names the branch, PR, and report.$SELF_BEFORE = self — the @malloydata/malloyyo version before release.
3. Worktree off fresh main
git -C ~/yo worktree add -b malloy-update-$V ~/yo-malloy-update-$V main
(The existing convention is a malloy-update-<version> branch — see the merged
#40 malloy-update-0.0.416.) Do all remaining work in ~/yo-malloy-update-$V.
4. Run the real update
cd ~/yo-malloy-update-$V
npm run --silent malloy-update -- --json > /tmp/malloy-update-real.json
cat /tmp/malloy-update-real.json
npm install here also populates this worktree's node_modules. Confirm
changed is true and primary matches $V; report the bump (from -> to
per package, lead with @malloydata/malloy). If preflight later complains about
missing deps, run npm install in the worktree and retry.
5. Preflight — STOP if red
npm run preflight
Green ("ALL CLEAR — Safe to push") → continue. Red → STOP, show the failing
step's output, leave the worktree in place so the user can inspect. Do not open
a PR on a red preflight.
6. Commit + PR
git -C ~/yo-malloy-update-$V add -A
git -C ~/yo-malloy-update-$V commit -m "Update to Malloy npm package $V"
git -C ~/yo-malloy-update-$V push -u origin malloy-update-$V
gh pr create --repo malloydata/malloyyo --base main --head malloy-update-$V \
--title "Update to Malloy npm package $V" \
--body "Update to Malloy npm package $V"
The diff should be exactly the three package.jsons + package-lock.json. Title
and body are exactly Update to Malloy npm package $V — no changelog, the diff
speaks for itself.
7. Wait for PR CI green — STOP if red
gh pr checks malloy-update-$V --repo malloydata/malloyyo --watch
Blocks until the preflight workflow (and DCO) finish. Green → continue.
Failed → STOP and report which check failed (don't merge a red PR).
8. Merge + wait for the release action
The repo merges with a merge commit (see #40), and touching
packages/cli/** / packages/mcp-engine/** on main triggers cli-publish.yml,
which patch-bumps and publishes @malloydata/malloyyo (committing a [skip ci]
bump back).
gh pr merge malloy-update-$V --repo malloydata/malloyyo --merge --delete-branch
gh run list --repo malloydata/malloyyo --workflow=cli-publish.yml --limit 1 \
--json databaseId,status,headBranch -q '.[0].databaseId'
gh run watch <run-id> --repo malloydata/malloyyo --exit-status
STOP and report if the release run fails.
9. Report the new published version
npm view @malloydata/malloyyo version
Report both edges, using the versions captured from the tool (no guessing):
Malloy $V in, @malloydata/malloyyo $SELF_BEFORE → $SELF_AFTER out.
10. Clean up
git -C ~/yo worktree remove ~/yo-malloy-update-$V
git -C ~/yo branch -D malloy-update-$V 2>/dev/null || true
git -C ~/yo pull --ff-only origin main
Then a short final summary: Malloy $V in, @malloydata/malloyyo $SELF_AFTER
out, worktree gone, main up to date.
