Skip to content

[cli] Do not show default settings when framework is detected#14608

Merged
onsclom merged 8 commits intomainfrom
austinmerrick/cli-do-not-show-default-project-settings-by-default
Jan 23, 2026
Merged

[cli] Do not show default settings when framework is detected#14608
onsclom merged 8 commits intomainfrom
austinmerrick/cli-do-not-show-default-project-settings-by-default

Conversation

@onsclom
Copy link
Copy Markdown
Contributor

@onsclom onsclom commented Jan 13, 2026

Default project settings are often not useful or confusing:
image

This PR hides those project settings when a framework is auto-detected, but still leaves the option to modify the settings

After:
image

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Jan 13, 2026

🦋 Changeset detected

Latest commit: c994841

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
vercel Patch

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 13, 2026

📦 CLI Tarball Ready

The Vercel CLI tarball for this PR is now available!

Quick Test

You can test this PR's CLI directly by running:

npx https://vercel-74pelin1d.vercel.sh/tarballs/vercel.tgz --help

Use in vercel.json

To use this CLI version in your project builds, add to your vercel.json:

{
  "build": {
    "env": {
      "VERCEL_CLI_VERSION": "vercel@https://vercel-74pelin1d.vercel.sh/tarballs/vercel.tgz"
    }
  }
}

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 13, 2026

🧪 Unit Test Strategy

Comparing: 8e4b946c994841 (view diff)

Strategy: Code changed outside of a package - running all unit tests

⚠️ All unit tests will run because global code changes could impact all packages.

Affected packages - 41 (100%)
  1. @vercel-internals/get-package-json
  2. @vercel/backends
  3. @vercel/build-utils
  4. @vercel/cervel
  5. @vercel/cli-auth
  6. @vercel/client
  7. @vercel/config
  8. @vercel/detect-agent
  9. @vercel/edge
  10. @vercel/elysia
  11. @vercel/error-utils
  12. @vercel/express
  13. @vercel/fastify
  14. @vercel/firewall
  15. @vercel/frameworks
  16. @vercel/fs-detectors
  17. @vercel/functions
  18. @vercel/gatsby-plugin-vercel-builder
  19. @vercel/go
  20. @vercel/h3
  21. @vercel/hono
  22. @vercel/hydrogen
  23. @vercel/introspection
  24. @vercel/koa
  25. @vercel/nestjs
  26. @vercel/next
  27. @vercel/node
  28. @vercel/oidc
  29. @vercel/oidc-aws-credentials-provider
  30. @vercel/python
  31. @vercel/python-analysis
  32. @vercel/redwood
  33. @vercel/related-projects
  34. @vercel/remix-builder
  35. @vercel/routing-utils
  36. @vercel/ruby
  37. @vercel/rust
  38. @vercel/static-build
  39. @vercel/static-config
  40. examples
  41. vercel

Results

  • Unit tests: All affected packages will run unit tests
  • E2E tests: Handled separately (Version Packages PRs or run-e2e-tests label)
  • Type checks: All affected packages will run type checks

This comment is automatically generated based on the affected testing strategy

Copy link
Copy Markdown
Contributor

@vercel vercel bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional Suggestion:

Default settings are not printed when a framework with a truthy slug (like Next.js) is detected due to an inverted condition.

Fix on Vercel

@onsclom onsclom marked this pull request as ready for review January 14, 2026 17:49
@onsclom onsclom requested a review from a team as a code owner January 14, 2026 17:49
Copy link
Copy Markdown
Contributor

@mehulkar mehulkar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nothing blocking, some qs

@onsclom onsclom enabled auto-merge (squash) January 23, 2026 20:37
@onsclom onsclom merged commit 3a1ea3f into main Jan 23, 2026
141 checks passed
@onsclom onsclom deleted the austinmerrick/cli-do-not-show-default-project-settings-by-default branch January 23, 2026 20:41
tknickman pushed a commit that referenced this pull request Jan 23, 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 the packages will
be published to npm automatically. 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.5.0

### Minor Changes

- New, consistent --format command for machine readable output
([#14609](#14609))

-   api command ([#14715](#14715))

- Detect Augment and OpenCode agents
([#14635](#14635))

### Patch Changes

- Track CLI as source for marketplace integration installations
([#14713](#14713))

- Do not show default project settings when framework is detected
([#14608](#14608))

- Fix flakey link tests caused by Inquirer type-ahead search
([#14716](#14716))

- Updated dependencies
\[[`64b4577b6d702335478af47c8395bf36daf4f311`](64b4577),
[`1ba97e3af1c1240703df3297fbbf7af0f809dd56`](1ba97e3)]:
    -   @vercel/python@6.3.1
    -   @vercel/detect-agent@1.1.0

## @vercel/detect-agent@1.1.0

### Minor Changes

- Detect Augment and OpenCode agents
([#14635](#14635))

## @vercel/python@6.3.1

### Patch Changes

- isInstalled check only needs to check for python on the path.
([#14712](#14712))

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants