Thanks to visit codestin.com
Credit goes to github.com

Skip to content

registry: add metabase-cli (npm:@metabase/cli)#10367

Closed
rolodato wants to merge 1 commit into
jdx:mainfrom
rolodato:registry-metabase-cli
Closed

registry: add metabase-cli (npm:@metabase/cli)#10367
rolodato wants to merge 1 commit into
jdx:mainfrom
rolodato:registry-metabase-cli

Conversation

@rolodato

@rolodato rolodato commented Jun 12, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown

What

Adds a registry short name for the official Metabase CLI, so users can mise use metabase-cli instead of mise use npm:@metabase/cli.

Popularity summary

  • Official CLI for Metabase (47.6k stars), published on npm under the @metabase org.
  • The CLI itself is new (first published 2026, latest release 0.1.12 on 2026-06-09, ~300 weekly npm downloads and growing) and actively developed by the Metabase team. I work at Metabase.

Backend choice

npm is the only distribution channel today — there are no GitHub release binaries yet, so no aqua/github option exists. I'm aware npm is a tier-3 backend with a very high bar; happy to close this if it doesn't meet it, or to revisit with a github/aqua primary backend once we ship standalone binaries. The package has no native dependencies and works with lifecycle scripts disabled.

Testing

Verified locally:

$ mise install npm:@metabase/cli@latest
mise npm:@metabase/[email protected] ✓ installed
$ mise exec npm:@metabase/cli@latest -- mb --version
0.1.12

Summary by CodeRabbit

  • Chores
    • Updated Metabase CLI package registry configuration with backend source definition and automated verification command.

@coderabbitai

coderabbitai Bot commented Jun 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 68f62f52-b476-430e-8fbb-ddb00091ccde

📥 Commits

Reviewing files that changed from the base of the PR and between 4628160 and de19d3e.

📒 Files selected for processing (1)
  • registry/metabase-cli.toml
📝 Walkthrough

Walkthrough

A new registry configuration file is added for the Metabase CLI package, specifying its npm backend source, descriptive metadata, and a version-check test command that validates against a templated version value.

Changes

Metabase CLI Registry Entry

Layer / File(s) Summary
Metabase CLI registry configuration
registry/metabase-cli.toml		 Registry entry for Metabase CLI is added with backends pointing to npm:@metabase/cli``, a description label, and a `test` command (`mb --version`) that expects a templated `{{version}}` value.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • jdx/mise#10258: Both PRs add new registry entries by defining backends, description, and a test command in registry/*.toml files.

Poem

🐰 A Metabase CLI joins the nest,
In registry, it takes its rest,
With npm source and test so tight,
The version check burns ever bright!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'registry: add metabase-cli (npm:@metabase/cli)' directly and clearly describes the main change: adding a registry entry for the Metabase CLI package with its npm source.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds registry/metabase-cli.toml mapping the short name metabase-cli to npm:@metabase/cli, the official Metabase CLI package. The entry is correctly formatted and consistent with comparable npm-backed registry entries (e.g., turbo.toml).

  • The TOML format, backends key, description, and test command (mb --version → {{version}}) all follow established conventions; no allow_builds options are needed since the package has no native compile steps.
  • The npm: backend is Tier 3 (requires Node.js on PATH) — the author explicitly acknowledges this in the PR description and notes no aqua/github binary distribution exists yet.

Confidence Score: 5/5

Safe to merge — a single, minimal TOML file with no logic changes and no impact on existing registry entries.

The change is a single three-line TOML file. The backends, description, and test fields are all well-formed and match the conventions used by other npm-backed entries. There is nothing in the file that could break existing tooling, and the acceptance of the npm tier-3 backend is an editorial decision for the maintainer.

No files require special attention.

Important Files Changed

Filename Overview
registry/metabase-cli.toml Adds a registry short name for the official Metabase CLI npm package; TOML format and test command are correct and consistent with similar npm-backed entries like turbo.toml

Reviews (1): Last reviewed commit: "registry: add metabase-cli (npm:@metabas..." | Re-trigger Greptile

@jdx jdx closed this Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@rolodato @jdx