Repository navigation
docs: describe the vercel connector setup in the beta changesets - #1202
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 5 Skipped Deployments
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
Risk score: Low (1/4)Assessed at 0335b83 from the changed files and the title, by
|
|
Thank you for following the naming conventions! 🙏 |
@evlog/cli
@evlog/eve
evlog
@evlog/nuxthub
@evlog/signals
@evlog/telemetry
commit: |
The next beta (#1168) would publish two contradictory entries about Vercel logs.
cli-logs-vercel-sourcesaysnpx evlog setup vercel"reuses a Vercel API-key connector the team already has or createsvercel/evlog", andlogs-explicit-vercel-connector(#1195) says "there is no defaultvercel/evlogany more", that the--jsonreusedfield "is replaced", and how "to keep reading throughvercel/evlog". None of that ever shipped:@evlog/cli@1.0.0-beta.3and@evlog/eve@1.0.0-beta.1on npm contain neither the Vercel source nor the evelogstool, 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-sourcegets the connector requirement and the setup flow,eve-logs-toolgets the no-connector failure. The bumps don't change: the CLI and evlog stay minor throughcli-logs-vercel-source, and@evlog/evestays minor througheve-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
The checked claims (
cli.LOGS_VERCEL_NO_CONNECTOR, the--connectorand--createflags, theVercel logs are not set upmessage) matchpackages/cli/srcon v3.pnpm content:lintscores both changesets 100. I checked the npm tarballs by grepping@evlog/cli@1.0.0-beta.3and@evlog/eve@1.0.0-beta.1forvercel/evlog,setup vercel,LOGS_VERCELandevlog__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.