Skip to content

docs: describe the vercel connector setup in the beta changesets - #1202

Merged
HugoRCD merged 1 commit into
v3from
changesets/vercel-connector-wording
Nov 21, 2026
Merged

HugoRCD merged 1 commit into
v3from
changesets/vercel-connector-wording

Conversation

@HugoRCD

@HugoRCD HugoRCD commented Nov 21, 2026

Copy link
Copy Markdown
Member

Written by an AI agent on behalf of @HugoRCD. @HugoRCD has not reviewed it yet.

The next beta (#1168) would publish two contradictory entries about Vercel logs. cli-logs-vercel-source says npx evlog setup vercel "reuses a Vercel API-key connector the team already has or creates vercel/evlog", and logs-explicit-vercel-connector (#1195) says "there is no default vercel/evlog any more", that the --json reused field "is replaced", and how "to keep reading through vercel/evlog". None of that ever shipped: @evlog/cli@1.0.0-beta.3 and @evlog/eve@1.0.0-beta.1 on npm contain neither the Vercel source nor the eve logs tool, so beta users never saw a default to lose.

This folds #1195's changeset into the two feature changesets, describing the behavior that ships: cli-logs-vercel-source gets the connector requirement and the setup flow, eve-logs-tool gets the no-connector failure. The bumps don't change: the CLI and evlog stay minor through cli-logs-vercel-source, and @evlog/eve stays minor through eve-logs-tool. No code changes.

To read the result, check the two files on this branch, or the beta.4 changelog in #1168 once the release workflow regenerates it after merge.

Before and after

$ git show origin/v3:.changeset/cli-logs-vercel-source.md | grep -o 'reuses.*vercel/evlog`'
reuses a Vercel API-key connector the team already has or creates `vercel/evlog`
$ git show HEAD:.changeset/cli-logs-vercel-source.md | grep -c 'creates `vercel/evlog`'
0

The checked claims (cli.LOGS_VERCEL_NO_CONNECTOR, the --connector and --create flags, the Vercel logs are not set up message) match packages/cli/src on v3. pnpm content:lint scores both changesets 100. I checked the npm tarballs by grepping @evlog/cli@1.0.0-beta.3 and @evlog/eve@1.0.0-beta.1 for vercel/evlog, setup vercel, LOGS_VERCEL and evlog__logs, with no match.

ELI5

The release notes for the next beta were going to say a feature "no longer" behaves a certain way, when nobody had ever used the old behavior. This rewrites the notes to just describe what the feature does.

@vercel

vercel Bot commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

5 Skipped Deployments
Project Deployment Actions Updated
evi Ignored Ignored Preview Nov 21, 2026 1:39pm UTC
evlog-docs Ignored Ignored v0 Nov 21, 2026 1:39pm UTC
evlog-render-lab Ignored Ignored Nov 21, 2026 1:39pm UTC
evlog-telemetry Ignored Ignored Nov 21, 2026 1:39pm UTC
just-use-evlog Ignored Ignored Nov 21, 2026 1:39pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 43ef905f-4f70-482f-a862-5ee8121203a3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions

Copy link
Copy Markdown
Contributor

Risk score: Low (1/4)

Assessed at 0335b83 from the changed files and the title, by scripts/risk-score. A new push replaces this score.

  • On merge: nothing ships or deploys
  • 3 files changed (19 lines), 0 of them tests
Area Level Why

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for following the naming conventions! 🙏

@pkg-pr-new

pkg-pr-new Bot commented Nov 21, 2026

Copy link
Copy Markdown
@evlog/cli

npm i https://pkg.pr.new/@evlog/cli@1202

@evlog/eve

npm i https://pkg.pr.new/@evlog/eve@1202

evlog

npm i https://pkg.pr.new/evlog@1202

@evlog/nuxthub

npm i https://pkg.pr.new/@evlog/nuxthub@1202

@evlog/signals

npm i https://pkg.pr.new/@evlog/signals@1202

@evlog/telemetry

npm i https://pkg.pr.new/@evlog/telemetry@1202

commit: 0335b83

@HugoRCD
HugoRCD added this pull request to the merge queue Nov 21, 2026
Merged via the queue into v3 with commit 05f5816 Nov 21, 2026
29 checks passed
@HugoRCD
HugoRCD deleted the changesets/vercel-connector-wording branch November 21, 2026 13:49
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.

1 participant