refactor(cli): use formatted tables for metrics schema output#15138
Merged
refactor(cli): use formatted tables for metrics schema output#15138
metrics schema output#15138Conversation
Replace raw CSV output with formatted tables using formatTable, matching the convention used by other list commands (domains ls, env ls, dns ls). Human-readable output now goes to stderr; JSON output remains on stdout. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: f5989a6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
📦 CLI Tarball ReadyThe Vercel CLI tarball for this PR is now available! Quick TestYou can test this PR's CLI directly by running: npx https://vercel-oef3tnrqu.vercel.sh/tarballs/vercel.tgz --helpUse in vercel.jsonTo use this CLI version in your project builds, add to your {
"build": {
"env": {
"VERCEL_CLI_VERSION": "vercel@https://vercel-oef3tnrqu.vercel.sh/tarballs/vercel.tgz"
}
}
}Python Runtime WheelA Python runtime wheel was also built for this PR. |
Contributor
🧪 Unit Test StrategyComparing: Strategy: Affected packages only ✅ Only testing packages that have been modified or depend on modified packages. Affected packages - 1 (3%)
Unaffected packages - 39 (98%)
Results
This comment is automatically generated based on the affected testing strategy |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Jooliashi
approved these changes
Feb 19, 2026
adriancooney
approved these changes
Feb 19, 2026
Merged
ctgowrie
pushed a commit
that referenced
this pull request
Feb 19, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## vercel@50.21.0 ### Minor Changes - Add `--all` flag to `vercel ls` command and improve behavior when not linked to a project ([#15143](#15143)) - `vercel ls` no longer requires a linked project. When not linked, it now lists all deployments across all projects in the current scope - Added `--all` flag to explicitly list deployments across all projects, even when linked to a specific project - Added "Project" column to the deployment table output to show which project each deployment belongs to - JSON output (`--format json`) is unchanged and continues to include the `name` field for project name ### Patch Changes - fix(cli): Handle SIGINT during upgrade prompt without showing a stacktrace ([#15105](#15105)) - Use formatted tables for `metrics schema` output, matching the convention used by other list commands ([#15138](#15138)) - Updated dependencies \[[`5d1f55af04d0fdba7e7ac86f9eeda44316f54f5b`](5d1f55a)]: - @vercel/next@4.15.31 ## @vercel/config@0.0.33 ### Patch Changes - Fix rewrite regexp conversion when header transforms are present ([#15134](#15134)) ## @vercel/next@4.15.31 ### Patch Changes - Added support for `regions` and `functionFailoverRegions` in per-function configuration from `vercel.json` for Next.js projects. ([#15149](#15149)) ## @vercel/python-runtime@0.4.3 ### Patch Changes - fix formatting and lint ([#15142](#15142)) <!-- VADE_RISK_START --> > [!NOTE] > Low Risk Change > > This PR is an automated Changesets release that only bumps version numbers in package.json files, updates CHANGELOG.md files, and deletes changeset markdown files - no code logic changes. > > - Version bumps in package.json files (vercel, @vercel/config, @vercel/next, @vercel/python-runtime) > - CHANGELOG.md updates documenting previous changes > - Deleted .changeset/*.md files consumed by release process > > <sup>Risk assessment for [commit 3b54c69](https://github.com/vercel/vercel/commit/3b54c6956719db3f1dfd50629330f42ab8143af6).</sup> <!-- VADE_RISK_END --> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace raw CSV output with formatted tables using formatTable, matching the convention used by other list commands (domains ls, env ls, dns ls). Human-readable output now goes to stderr; JSON output remains on stdout.
Note
Low Risk Change
This PR refactors CLI output formatting from CSV to formatted tables for the metrics schema command, with no security, auth, or business logic changes.
Risk assessment for commit f5989a6.