Skip to content

fix: vercel deployment#27

Merged
weaponsforge merged 2 commits into
devfrom
fix/vercel-deployment
Apr 18, 2026
Merged

fix: vercel deployment#27
weaponsforge merged 2 commits into
devfrom
fix/vercel-deployment

Conversation

@weaponsforge
Copy link
Copy Markdown
Owner

@weaponsforge weaponsforge commented Apr 18, 2026

Summary

  • Update the Vercel CLI to v51.7.0 (latest version), fixing the recent Vercel deployment error where it detects mismatching Node v22 and v24 versions

Type of Change

  • Bug fix
  • Other (please describe): CI/CD

Checklist

Screenshots

vercel-fail

Summary by CodeRabbit

  • Chores
    • Updated server package to version 1.1.3
    • Updated CI/CD deployment tools to latest versions

Fixes the error during deployment:

Found invalid Node.js Version: ">=24". Please set
"engines": { "node": "22.x" } in your `package.json` file
to use Node.js 22
- Remove test branch deployment trigger
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 18, 2026

📝 Walkthrough

Walkthrough

This pull request updates the Vercel CLI version in the GitHub Actions release workflow from 47.0.6 to 51.7.0, and bumps the server package version from 1.1.2 to 1.1.3. These are straightforward version updates with no functional or dependency changes.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow
.github/workflows/release.yml
Updated Vercel CLI installation from version 47.0.6 to 51.7.0 in the release workflow.
Package Version
server/package.json
Incremented server package version from 1.1.2 to 1.1.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop hop, the versions climb so high,
From 47 to 51 they fly!
1.1.2 to 1.1.3, what a treat,
Another release, oh so neat!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'fix: vercel deployment' is vague and generic, using a broad term that doesn't specify what aspect of the Vercel deployment was fixed or what the actual change accomplishes. Consider a more specific title like 'fix: update Vercel CLI to v51.7.0 to resolve Node.js version mismatch' that clearly indicates the specific fix being applied.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/vercel-deployment

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@weaponsforge weaponsforge merged commit 007bd10 into dev Apr 18, 2026
2 checks passed
@weaponsforge weaponsforge deleted the fix/vercel-deployment branch April 18, 2026 09:34
@weaponsforge weaponsforge mentioned this pull request Apr 18, 2026
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