@metabase/cli 0.5.5 → 0.5.6

package/dist/{verify-k0WHgc16.mjs → verify-D9i63gmK.mjs}

@@ -1,7 +1,7 @@
-import { n as createClient } from "./client-D2ycdMRO.mjs";
+import { n as createClient } from "./client-BN93yUlt.mjs";
 import { g as errorMessage, l as MetabaseError, p as TimeoutError, u as NetworkError } from "./predicates-0C0TsWcJ.mjs";
 import { K as HttpError } from "./cli.mjs";
-import { B as probeServer, E as USER_AGENT } from "./runtime-D5yfliIq.mjs";
+import { B as probeServer, E as USER_AGENT } from "./runtime-CEAFobLj.mjs";
 //#region src/core/auth/verify.ts
 const VERIFY_TIMEOUT_MS = 15e3;
 async function verifyAndProbe(url, credential, options = {}) {

package/dist/{verify-CMTrDvAW.mjs → verify-DS0REVed.mjs}

@@ -1,6 +1,6 @@
 import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
 import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { t as defineMetabaseCommand } from "./runtime-CEAFobLj.mjs";
 import { t as ModerationReview } from "./moderation-review-Bf9bPNQI.mjs";
 import { i as moderationReviewView, n as verifyFlags, r as describeReview, t as reviewInput } from "./verify-flags-DEVMB9w0.mjs";
 //#region src/commands/card/verify.ts

package/dist/{wait-C69z8PSw.mjs → wait-DrOL01Y_.mjs}

@@ -1,7 +1,7 @@
 import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
-import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-vxN__4cz.mjs";
-import { r as parseWaitSchedule } from "./wait-flags-C3cu_O0w.mjs";
+import { t as defineMetabaseCommand } from "./runtime-CEAFobLj.mjs";
+import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-uailHW3t.mjs";
+import { r as parseWaitSchedule } from "./wait-flags-DT1zA69Z.mjs";
 import { u as syncTaskView } from "./git-sync-D1aKczo6.mjs";
 import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask, r as syncTaskIdleView, t as SyncTaskOrIdle } from "./sync-task-Gf86CU9l.mjs";
 //#region src/commands/git-sync/wait.ts

package/dist/{wait-flags-C3cu_O0w.mjs → wait-flags-DT1zA69Z.mjs}

@@ -1,6 +1,6 @@
 import { t as interruptSignal } from "./cli.mjs";
 import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-vxN__4cz.mjs";
+import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-uailHW3t.mjs";
 //#region src/commands/wait-flags.ts
 const waitScheduleFlags = {
 	timeout: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/cli",
-  "version": "0.5.5",
+  "version": "0.5.6",
   "description": "Metabase CLI",
   "license": "AGPL-3.0",
   "repository": {

package/skill-data/data-app/SKILL.md

@@ -39,7 +39,7 @@ mb data-app create --body '{"name":"sales-overview","display_name":"Sales overvi
 mb data-app scaffold <repo>/data_apps/sales-overview && cd <repo>/data_apps/sales-overview
 ```
 
-`scaffold [dir]` takes a **directory**, not the slug: it copies the Vite + React + TypeScript template into a new or empty directory (the current one when omitted) and needs no server. When the instance syncs with a git repository (`mb git-sync status`), the directory is `data_apps/<slug>/` in a local clone of that repository (ask the user for its path, or clone the remote), where an export writes the app's `data_app.yaml` and bundle: an export leaves the source alone and an import ignores it, so the repository keeps the source with the app. `scaffold` needs an empty directory, so scaffold before the app's first export; for an app already in the repository, scaffold into a new directory and copy its files, dotfiles included (`cp -R <dir>/. data_apps/<slug>/`), in beside `data_app.yaml` and `dist/`; check `.gitignore` is there before `npm install`. Without a repository, use any new directory, and once remote sync is set up, move the project (without `node_modules/`, `dist/`, `.env.local` and a hand-written `data_app.yaml`) into `data_apps/<slug>/` before committing its source. Then install the SDK, then the rest:
+`scaffold [dir]` takes a **directory**, not the slug: it copies the Vite + React + TypeScript template into a new or empty directory (the current one when omitted) and needs no server. When the instance syncs with a git repository (`mb git-sync status`), the directory is `data_apps/<slug>/` in a local clone of that repository (ask the user for its path, or clone the remote), where an export writes the app's `data_app.yaml` and bundle: an export leaves the source alone and an import ignores it, so the repository keeps the source with the app. `scaffold` needs an empty directory, so scaffold before the app's first export; for an app already in the repository, scaffold into a new directory and copy its files, dotfiles included (`cp -R <dir>/. data_apps/<slug>/`), in beside `data_app.yaml` and `dist/`; check `.gitignore` is there before `npm install`. Without a repository, use any new directory, and once remote sync is set up, move the project (without `node_modules/`, `build/`, `dist/`, `.env.local` and a hand-written `data_app.yaml`) into `data_apps/<slug>/` before committing its source. Then install the SDK, then the rest:
 
 ```bash
 npm install @metabase/embedding-sdk-react@<major>-beta   # <major>: 66 for a version tag v1.66.x (`mb auth status --profile <name> --json | jq -r .version.tag`)
@@ -112,7 +112,7 @@ npm run typecheck && npm run build
 mb data-app set-bundle sales-overview
 ```
 
-`set-bundle` uploads `dist/index.js` (`--bundle` for another path) and replaces the app's bundle, live at once. A new app is on from the start; `mb data-app set-enabled <slug> false` turns it off, which only the user decides. An app turned off opens only in Data Studio → Data apps → the app → Overview; `/apps/<slug>` says "not found", for admins too. Give the user `<metabase-url>/apps/<slug>`.
+`set-bundle` uploads `build/index.js`, the file `npm run build` writes (`--bundle` for another path), and replaces the app's bundle, live at once. A new app is on from the start; `mb data-app set-enabled <slug> false` turns it off, which only the user decides. An app turned off opens only in Data Studio → Data apps → the app → Overview; `/apps/<slug>` says "not found", for admins too. Give the user `<metabase-url>/apps/<slug>`.
 
 A viewer needs one of their groups assigned to the app (otherwise "You don't have access"), which only the user can do (Data Studio → Data apps → the app → Permissions). A group reaches the app's collection and nothing more, so a viewer also needs data access to the tables its questions read.
 
@@ -133,5 +133,5 @@ A viewer needs one of their groups assigned to the app (otherwise "You don't hav
 
 - **Turn off:** `mb data-app set-enabled <slug> false`. **Rename:** `mb data-app update <slug> --body '{"display_name":"…"}'` (also `description`, `allowed_hosts`).
 - **Outdated:** an app Data Studio lists as _Outdated_ targets an older data-app contract: it won't open for anyone, and only admins see it, until it's migrated. Tell the user; don't change its code ad hoc.
-- **Move to another instance:** the app, its collection and what the collection holds are git-synced content. `mb git-sync export` (`git-sync`) writes `data_apps/<slug>/` with the bundle, and the collection under `collections/data_apps/`; importing the repository on the other instance recreates them with the same entity IDs, so the same `src/metabase.ts` works there. The first import there creates the app on, like `create`, open to admins until the user assigns groups; later imports keep its on/off state. The import doesn't check that the questions' tables are published on that instance, so the Library content they read goes in the same export: flag the Library root once (`mb git-sync add-collection <library-id>`, `git-sync`), or its metrics, measures and segments stay out of the repository; a data action needs its database's toggle on there too. Once the app is done, commit its source in `data_apps/<slug>/` on the branch you exported to, after the export. Pull the export branch: `git restore` a modified `dist/index.js`, then `git fetch`, `git switch <branch>`, `git pull --ff-only`. Then `git add data_apps/<slug>`, commit and push, and `mb git-sync import` whatever a cached `has-remote-changes` says, or the next export ends in `conflict`. The export writes `data_app.yaml` and `dist/index.js`, the bundle you uploaded; never edit or commit those two yourself, and when a fresh build changes `dist/index.js`, set the bundle and export again instead. The template's `.gitignore` keeps `node_modules/` and `.env.local` out. On a read-only synced instance only `set-enabled` works: creating, bundling, updating and deleting an app answer 403, and so does editing its collection; change it where it was built and export again.
+- **Move to another instance:** the app, its collection and what the collection holds are git-synced content. `mb git-sync export` (`git-sync`) writes `data_apps/<slug>/` with the bundle, and the collection under `collections/data_apps/`; importing the repository on the other instance recreates them with the same entity IDs, so the same `src/metabase.ts` works there. The first import there creates the app on, like `create`, open to admins until the user assigns groups; later imports keep its on/off state. The import doesn't check that the questions' tables are published on that instance, so the Library content they read goes in the same export: flag the Library root once (`mb git-sync add-collection <library-id>`, `git-sync`), or its metrics, measures and segments stay out of the repository; a data action needs its database's toggle on there too. Once the app is done, commit its source in `data_apps/<slug>/` on the branch you exported to, after the export. Pull the export branch: `git fetch`, `git switch <branch>`, `git pull --ff-only`. Then `git add data_apps/<slug>`, commit and push, and `mb git-sync import` whatever a cached `has-remote-changes` says, or the next export ends in `conflict`. The export writes `data_app.yaml` and `dist/index.js`, the bundle you uploaded; never edit those two, and leave them out of your commits unless the bundle ships through git (below). The template's `.gitignore` keeps `node_modules/`, `build/` and `.env.local` out. A bundle can instead ship through git, from CI say: `npm run build:ci` writes `dist/index.js`, and once that is committed and pushed, the next import loads it. On a read-only synced instance only `set-enabled` works: creating, bundling, updating and deleting an app answer 403, and so does editing its collection; change it where it was built and export again.
 - **Delete:** confirm with the user, then `mb data-app delete <slug> --yes` — it removes the app, its bundle, its collection and the questions and actions in it. The project directory stays: in a synced repository, the next export removes the app's `data_app.yaml`, bundle and collection files; after that export, switch and pull the same way, delete the source in `data_apps/<slug>/` in a commit of your own, push, and import.

package/skill-data/data-app/template/README.md

@@ -20,10 +20,14 @@ npm install
 ```bash
 npm run dev         # preview at http://localhost:5174, in the sandbox Metabase runs apps in
 npm run typecheck   # type-checks src/ and vite.config.ts
-npm run build       # builds dist/index.js
+npm run build       # builds build/index.js
 mb data-app typed-schema <slug> --out src/metabase.ts   # the app's queries and actions
-mb data-app set-bundle <slug>                     # makes dist/index.js the app's bundle
+mb data-app set-bundle <slug>                     # makes build/index.js the app's bundle
 ```
 
+To ship the bundle through git instead, for example from CI, run
+`npm run build:ci` and commit `dist/index.js`, the file the app's
+`data_app.yaml` names; the next git-sync import loads it.
+
 `npm run dev` reads `DATA_APP_MB_URL` and `DATA_APP_MB_API_KEY` from
 `.env.local`; `.env.local.example` lists them.

package/skill-data/data-app/template/gitignore

@@ -1,5 +1,5 @@
 node_modules
-dist
+build
 .env.local
 .vite
 .idea

package/skill-data/data-app/template/package.json

@@ -6,6 +6,7 @@
   "scripts": {
     "dev": "vite",
     "build": "vite build",
+    "build:ci": "vite build --outDir dist",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {

package/skill-data/mbql/SKILL.md

@@ -49,7 +49,7 @@ An options key the server doesn't know is rejected or silently dropped, never ap
 - `filters` are ANDed; OR is `["or", {}, a, b, …]`. Multi-value is `["in", {}, <field>, "a", "b"]` / `["not-in", …]`.
 - Relative dates: `["time-interval", {}, <field>, -30, "day"]`, `["time-interval", {}, <field>, "current", "month"]`. A stated year or date range is absolute: `["between", {}, <field>, "2024-01-01", "2024-12-31"]` (inclusive).
 - `aggregation` is a list of aggregation clauses, `breakout` a list of refs. "only / where X" is a filter; "by / per / over time" is a breakout.
-- Name every aggregation a later stage, a chart setting or a target table reads: `["sum", {"name": "revenue", "display-name": "Revenue"}, <field>]`. Unnamed, it is `count`, `sum`, `avg`, … and a second `sum` is `sum_2`.
+- An unnamed aggregation is `count`, `sum`, `avg`, …, a breakout keeps its field's name, and a repeat gets a suffix that moves when clauses change: a second `sum` is `sum_2`, a second `ID` breakout (another table's) `ID_2`. When a later stage, a chart setting or a target table reads such a column, set `"name"` in the clause's options: `["sum", {"name": "revenue", "display-name": "Revenue"}, <field>]`, `["field", {"name": "product_id", "source-field": 11}, 12]`.
 - An aggregation can be arithmetic over aggregations: `["/", {"name": "aov"}, ["sum", {}, <field>], ["count", {}]]`.
 - Date arithmetic is `["datetime-diff", {}, a, b, "day"]`.
 
@@ -122,7 +122,7 @@ A later stage reads the previous stage's output by column name, with the column'
 ]
 ```
 
-The names and base types are the `name` and `base_type` of the columns the earlier stages return: run them once (`mb query … --json`, `data.cols`) and copy both. A breakout keeps its field's name (`CREATED_AT`, even when bucketed); an aggregation has the `name` you gave it.
+The names and base types are the `name` and `base_type` of the columns the earlier stages return: run them once (`mb query … --json`, `data.cols`) and copy both. A breakout keeps its field's name (`CREATED_AT`, even when bucketed) and an aggregation its operator's, unless its options set `name`.
 
 **Window:** `offset` sits in `aggregation` and reads another breakout row. Month-over-month against a monthly breakout:
 

package/dist/git-sync-DaHnqpYi.mjs

@@ -1,29 +0,0 @@
-import { t as defineCommandGroup } from "./group--6adAsqG.mjs";
-//#region src/commands/git-sync/index.ts
-var git_sync_default = defineCommandGroup({
-	name: "git-sync",
-	description: "Sync Metabase content with a git remote",
-	skills: [{
-		skill: "git-sync",
-		purpose: "import/export round-trip and dirty checks"
-	}],
-	subCommands: {
-		status: () => import("./status-CcOJIgfB.mjs").then((mod) => mod.default),
-		"is-dirty": () => import("./is-dirty-BXwvuTeD.mjs").then((mod) => mod.default),
-		"has-remote-changes": () => import("./has-remote-changes-d_JyzdPX.mjs").then((mod) => mod.default),
-		dirty: () => import("./dirty-1taTj3G6.mjs").then((mod) => mod.default),
-		"current-task": () => import("./current-task-DB7UTh6J.mjs").then((mod) => mod.default),
-		"cancel-task": () => import("./cancel-task-CpZcj7HB.mjs").then((mod) => mod.default),
-		wait: () => import("./wait-C69z8PSw.mjs").then((mod) => mod.default),
-		import: () => import("./import-1bK-qrjV.mjs").then((mod) => mod.default),
-		export: () => import("./export-B0NUSP6q.mjs").then((mod) => mod.default),
-		"export-preflight": () => import("./export-preflight-Bbl1bHpI.mjs").then((mod) => mod.default),
-		stash: () => import("./stash-BGqpcbSW.mjs").then((mod) => mod.default),
-		branches: () => import("./branches-CkOAJk1H.mjs").then((mod) => mod.default),
-		"create-branch": () => import("./create-branch-CKQkpU-_.mjs").then((mod) => mod.default),
-		"add-collection": () => import("./add-collection-lgBkahhW.mjs").then((mod) => mod.default),
-		"remove-collection": () => import("./remove-collection-dltKu8LO.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { git_sync_default as default };

package/dist/signal-BNUlQjpc.mjs

@@ -1,25 +0,0 @@
-import { g as errorMessage, i as AbortError, l as MetabaseError } from "./predicates-0C0TsWcJ.mjs";
-//#region ../client/src/signal.ts
-function combineAborts(...signals) {
-	return AbortSignal.any(signals.filter((signal) => signal !== void 0));
-}
-function throwIfAborted(...signals) {
-	for (const signal of signals) if (signal?.aborted) throw abortReason(signal);
-}
-function abortReason(signal) {
-	const reason = signal.reason;
-	if (reason instanceof MetabaseError) return reason;
-	if (reason instanceof Error || typeof reason === "string") return new AbortError(errorMessage(reason) || "aborted");
-	return new AbortError("aborted");
-}
-function untilAborted(promise, signal) {
-	if (signal === void 0) return promise;
-	throwIfAborted(signal);
-	return new Promise((resolve, reject) => {
-		const onAbort = () => reject(abortReason(signal));
-		signal.addEventListener("abort", onAbort, { once: true });
-		promise.then(resolve, reject).finally(() => signal.removeEventListener("abort", onAbort));
-	});
-}
-//#endregion
-export { throwIfAborted as n, untilAborted as r, combineAborts as t };

package/dist/table-nIdBLcz7.mjs

@@ -1,26 +0,0 @@
-import { t as defineCommandGroup } from "./group--6adAsqG.mjs";
-//#region src/commands/table/index.ts
-var table_default = defineCommandGroup({
-	name: "table",
-	description: "Manage Metabase tables",
-	skills: [{
-		skill: "metadata",
-		purpose: "table and column metadata, semantic types, visibility"
-	}],
-	subCommands: {
-		list: () => import("./list-BWNw-ppI.mjs").then((m) => m.default),
-		get: () => import("./get-DGlZtzfB.mjs").then((m) => m.default),
-		fields: () => import("./fields-M66PaKdV.mjs").then((m) => m.default),
-		fks: () => import("./fks-BvOGzID5.mjs").then((m) => m.default),
-		update: () => import("./update-BsEG1dRm.mjs").then((m) => m.default),
-		"sync-schema": () => import("./sync-schema-BJ-AtcCq.mjs").then((m) => m.default),
-		"rescan-values": () => import("./rescan-values-0-c5Gqtx.mjs").then((m) => m.default),
-		"discard-values": () => import("./discard-values-DmiWAx4J.mjs").then((m) => m.default),
-		"bulk-edit": () => import("./bulk-edit-CLJeGY2E.mjs").then((m) => m.default),
-		"bulk-sync-schema": () => import("./bulk-sync-schema-CN797vy9.mjs").then((m) => m.default),
-		"bulk-rescan-values": () => import("./bulk-rescan-values-DsaGKIo_.mjs").then((m) => m.default),
-		"bulk-discard-values": () => import("./bulk-discard-values-D4eFBtKc.mjs").then((m) => m.default)
-	}
-});
-//#endregion
-export { table_default as default };

package/dist/transform-job-sCgr8r-t.mjs

@@ -1,22 +0,0 @@
-import { t as defineCommandGroup } from "./group--6adAsqG.mjs";
-//#region src/commands/transform-job/index.ts
-var transform_job_default = defineCommandGroup({
-	name: "transform-job",
-	description: "Manage Metabase transform jobs",
-	skills: [{
-		skill: "transform",
-		purpose: "tag-driven job schedules"
-	}],
-	subCommands: {
-		list: () => import("./list-TzuL_7GA.mjs").then((mod) => mod.default),
-		get: () => import("./get-SOCVdBIU.mjs").then((mod) => mod.default),
-		create: () => import("./create-Cc07ouKB.mjs").then((mod) => mod.default),
-		update: () => import("./update-CsH0lSpQ2.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-B9GABYEJ.mjs").then((mod) => mod.default),
-		run: () => import("./run-Cf1nJahe.mjs").then((mod) => mod.default),
-		transforms: () => import("./transforms-D1wwWdCY.mjs").then((mod) => mod.default),
-		"set-active": () => import("./set-active-BQjKw1wk.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_job_default as default };

package/dist/transform-l1oC8oUS.mjs

@@ -1,28 +0,0 @@
-import { t as defineCommandGroup } from "./group--6adAsqG.mjs";
-//#region src/commands/transform/index.ts
-var transform_default = defineCommandGroup({
-	name: "transform",
-	description: "Manage Metabase transforms",
-	skills: [{
-		skill: "transform",
-		purpose: "body shape, run-with-wait, iterate"
-	}, {
-		skill: "mbql",
-		purpose: "MBQL source.query bodies"
-	}],
-	subCommands: {
-		list: () => import("./list-DSi8mf_F.mjs").then((mod) => mod.default),
-		get: () => import("./get-Bt2Q516N.mjs").then((mod) => mod.default),
-		dependencies: () => import("./dependencies-BcPdAMYB.mjs").then((mod) => mod.default),
-		create: () => import("./create-Dr-q5oWx2.mjs").then((mod) => mod.default),
-		update: () => import("./update-Cga4lrX5.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-TcDfZNz2.mjs").then((mod) => mod.default),
-		"delete-table": () => import("./delete-table-a8acciQe.mjs").then((mod) => mod.default),
-		run: () => import("./run-BS_wUAsi.mjs").then((mod) => mod.default),
-		cancel: () => import("./cancel-CRpzqIUu.mjs").then((mod) => mod.default),
-		"get-run": () => import("./get-run-BZP_z57v.mjs").then((mod) => mod.default),
-		runs: () => import("./runs-BJ4uy05c.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_default as default };