Skip to content

Fix web image workspace patch inputs - #116

Merged
kl3inIT merged 1 commit into
mainfrom
fix/web-docker-pnpm-patches
Jul 28, 2026
Merged

Fix web image workspace patch inputs#116
kl3inIT merged 1 commit into
mainfrom
fix/web-docker-pnpm-patches

Conversation

@kl3inIT

@kl3inIT kl3inIT commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Cause

The root pnpm lockfile now declares deterministic Fumadocs patches. �pps/web/Dockerfile copied that lockfile but not patches/, so the production web-image build failed with ENOENT even though ordinary web CI was green.

Fix

  • copy patches/ before the filtered workspace install
  • rebuild web images when any copied workspace package manifest or patch changes
  • make Deployment contracts execute the web Docker build stage so missing Docker-context inputs fail before merge

Verification

  • actionlint 1.7.12
  • full Node 24 �pps/web/Dockerfile --target build completed, including frozen pnpm install, OpenAPI generation, Oxlint, TypeScript, and Vite production build
  • git diff --check

This does not dispatch or perform a deployment.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 8 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 6d11ea4e-2940-4a98-8594-0bfa86404b44

📥 Commits

Reviewing files that changed from the base of the PR and between a1f59e1 and 6248ad1.

📒 Files selected for processing (3)
  • .github/workflows/build-images.yml
  • .github/workflows/ci.yml
  • apps/web/Dockerfile
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/web-docker-pnpm-patches

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.

@kl3inIT
kl3inIT merged commit 24ad760 into main Jul 28, 2026
14 checks passed
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