Skip to content

fix(build): unblock prod deploy — skip redundant ESLint in next build + site-profile MCP tools - #55

Merged
Tatenda merged 1 commit into
mainfrom
develop
Jul 11, 2026
Merged

fix(build): unblock prod deploy — skip redundant ESLint in next build + site-profile MCP tools#55
Tatenda merged 1 commit into
mainfrom
develop

Conversation

@Tatenda

@Tatenda Tatenda commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Merges develop → main. Includes the site-profile MCP tools (get_site_profile / set_site_profile) and the build fix (eslint.ignoreDuringBuilds — CI still lints via yarn check-all). Preview build now green.

🤖 Generated with Claude Code

The Vercel production build failed on prettier/prettier ESLint errors —
pure union-type formatting the build-integrated eslint-plugin-prettier
wants collapsed, opposite to what the pinned prettier 3.6.2 (and CI's
`prettier --check`) wants. The two are mutually exclusive, so the files
can't satisfy both. CI's `yarn check-all` (typecheck + next lint +
prettier --check) already gates lint/format on every PR, so ESLint inside
`next build` is redundant. Disable it; tsc still runs during the build.

Unblocks the site-profile MCP tools (get_site_profile / set_site_profile)
deploy to prod.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Tatenda
Tatenda merged commit 60b5fb5 into main Jul 11, 2026
4 checks passed
@vercel

vercel Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated (UTC)
music-next Ready Ready Preview, Comment Jul 11, 2026 8:50am

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Tatenda, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 94f7307a-272f-4e6e-a999-dcbd91d5abde

📥 Commits

Reviewing files that changed from the base of the PR and between 1d9b119 and 4ad5691.

📒 Files selected for processing (1)
  • next.config.mjs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

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.

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