Skip to content

Conversation

@piyush-jaiswal
Copy link
Owner

@piyush-jaiswal piyush-jaiswal commented Aug 22, 2025

Summary by CodeRabbit

  • Chores
    • Deployment pipeline updated to use a split-tgz archive for both preview and production, enabling faster and more efficient artifact uploads.
    • No user-facing changes; app behavior unchanged.
    • No action required from users.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 22, 2025

Walkthrough

Replaces Vercel deploy packaging with the split-tgz archive option and adds a comment referencing the Vercel changelog in both preview and production GitHub Actions workflows. No other workflow steps or public API/signatures changed.

Changes

Cohort / File(s) Summary of Changes
Vercel deploy workflows
.github/workflows/deploy_preview.yml, .github/workflows/deploy_production.yml
Updated the vercel deploy command to include --archive=split-tgz alongside --prebuilt (and --prod in production). Added a comment line referencing the Vercel changelog before the Deploy step. No other workflow steps modified.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor Dev as Developer
    participant GH as GitHub Actions
    participant CLI as Vercel CLI
    participant API as Vercel Platform

    Dev->>GH: Push / Merge
    GH->>CLI: Run `vercel deploy --prebuilt --archive=split-tgz` [--prod]
    note right of CLI #f6f8ff: Package artifacts as split-tgz (new)
    CLI->>API: Upload split-tgz archive & initiate deployment
    API-->>GH: Deployment status (URL / success / error)
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

I packed our bytes in split-tgz cheer,
Hopped to Vercel, the path now clear.
Preview, Prod—both zipped just so,
Carrots cached and ready to go.
Thump! A deploy, concise and near. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 83fc6f9 and 1d648a9.

📒 Files selected for processing (2)
  • .github/workflows/deploy_preview.yml (1 hunks)
  • .github/workflows/deploy_production.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • .github/workflows/deploy_production.yml
  • .github/workflows/deploy_preview.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: deploy-preview
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ci/archive-build

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
.github/workflows/deploy_preview.yml (2)

39-41: Make deploy fully non-interactive in CI with --yes.

The CLI can prompt on first-time setups; adding --yes keeps the step deterministic.
Apply:

-              run: vercel deploy --prebuilt --archive=tgz --token=${{ secrets.VERCEL_TOKEN }}
+              run: vercel deploy --prebuilt --archive=tgz --yes --token=${{ secrets.VERCEL_TOKEN }}

(vercel.com)


39-41: If you hit upload limits or slow uploads, consider split-tgz.

Vercel introduced --archive=split-tgz (Jan 16, 2025) to bypass single-file size limits and speed up large prebuilt uploads (~up to 30% faster). Optional switch if your build output is huge.

Example:

-              run: vercel deploy --prebuilt --archive=tgz --token=${{ secrets.VERCEL_TOKEN }}
+              run: vercel deploy --prebuilt --archive=split-tgz --yes --token=${{ secrets.VERCEL_TOKEN }}

(vercel.com)

.github/workflows/deploy_production.yml (2)

37-39: Add --yes for non-interactive prod deploys.

Prevents any unexpected prompts during production releases.

-              run: vercel deploy --prebuilt --archive=tgz --prod --token=${{ secrets.VERCEL_TOKEN }}
+              run: vercel deploy --prebuilt --archive=tgz --prod --yes --token=${{ secrets.VERCEL_TOKEN }}

(vercel.com)


37-39: Option: switch to split-tgz for very large artifacts.

If production bundles are massive or deployments are hitting upload limits, --archive=split-tgz can help.

-              run: vercel deploy --prebuilt --archive=tgz --prod --token=${{ secrets.VERCEL_TOKEN }}
+              run: vercel deploy --prebuilt --archive=split-tgz --prod --yes --token=${{ secrets.VERCEL_TOKEN }}

(vercel.com)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4e166d6 and 83fc6f9.

📒 Files selected for processing (2)
  • .github/workflows/deploy_preview.yml (1 hunks)
  • .github/workflows/deploy_production.yml (1 hunks)
🔇 Additional comments (2)
.github/workflows/deploy_preview.yml (1)

39-41: LGTM: Using tgz archive with prebuilt deploys is correct and supported.

This reduces file-count uploads and helps avoid rate limits for large prebuilt outputs. Official docs show the exact pattern: vercel deploy --prebuilt --archive=tgz. (vercel.com)

.github/workflows/deploy_production.yml (1)

37-39: LGTM: Aligning production deploy with tgz archive is a good move.

Matches the preview workflow and follows the documented --archive=tgz usage for prebuilt deployments. (vercel.com)

@piyush-jaiswal piyush-jaiswal merged commit 14e4990 into master Aug 22, 2025
4 of 5 checks passed
@piyush-jaiswal piyush-jaiswal deleted the ci/archive-build branch August 22, 2025 11:12
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.

2 participants