Updated vercel synv env vars example

[D-K-P]

Summary by CodeRabbit

• New Features

  • Enhanced Vercel integration now automatically leverages environment-based configuration for secure authentication and project identification, ensuring more reliable deployments.

• Documentation

  • Added a new page for "upgrade-to-v4" in the "Getting started" section.
  • Improved formatting of documentation for better readability without altering content.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e006cdb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

This update modifies the syncVercelEnvVars() function call in the build configuration to include an object with three properties—vercelAccessToken, projectId, and vercelTeamId—sourced from environment variables. The API of the exported function in @trigger.dev/build/extensions/core has been updated accordingly. Documentation in docs/guides/examples/vercel-sync-env-vars.mdx was also revised to reflect these changes. Additionally, the docs/docs.json file was reformatted for improved readability, with several "pages" arrays consolidated into single lines and a new page added to the "Getting started" group.

Changes

File(s) / Component	Change Summary
trigger.config.ts and @trigger.dev/build/extensions/core	Updated the syncVercelEnvVars() invocation to accept an object with vercelAccessToken, projectId, and vercelTeamId parameters, allowing direct configuration for Vercel API integration.
docs/guides/examples/vercel-sync-env-vars.mdx	Revised documentation to mirror the updated function signature and provide guidance on the new parameters sourced from environment variables.
docs/docs.json	Reformatted "pages" arrays for various groups into a single line, added the "upgrade-to-v4" page in "Getting started", and updated multiple page signatures across different groups without affecting functionality.

Sequence Diagram(s)

sequenceDiagram
    participant T as Trigger Config
    participant S as syncVercelEnvVars
    participant V as Vercel API

    T->>S: Call syncVercelEnvVars({vercelAccessToken, projectId, vercelTeamId})
    S->>V: Send authentication & project details
    V-->>S: Return response/status
    S-->>T: Acknowledge sync result

Loading

Poem

I'm a bouncing rabbit with a gleeful cheer,
Hopping through code with environment details near.
Tokens and IDs now in a neat, clear bundle,
Each hop aligns our integration like a well-set candle.
Cheers to the sync that makes our work so dear!
🐇🌟

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9f7dc05 and e006cdb.

📒 Files selected for processing (1)

• docs/docs.json (10 hunks)

✅ Files skipped from review due to trivial changes (1)

• docs/docs.json

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (javascript-typescript)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.