ci: disable free-disk-space for up-features job

[skevetter]

Problem

Test up-features on ubuntu-latest failed with:

inspect image temp-2086554238-ccd77:devsy-82658532b00e76c6eb8cfb6b10913fb8: image not found

https://github.com/devsy-org/devsy/actions/runs/32018882285/job/95361185253

Root cause

The full job log (fetched via gh api .../actions/jobs/95361185253/logs) shows the build succeeding and the image being verified present, then ~14–25s later, while the jlumbroso/free-disk-space step (running with background: true) was still pruning Docker images concurrently:

10:44:05.563  #12 naming to docker.io/library/temp-2086554238-ccd77:devsy-8265...  done
10:44:31.295  INFO inspecting image: image=temp-2086554238-ccd77:devsy-8265...
10:44:31.299  Deleted Images: untagged: ghcr.io/github/github-mcp-server:latest ...
10:44:41.298  ERROR ... image not found

The freshly built, not-yet-referenced-by-a-container image got swept up by the background disk-cleanup's docker image prune before the container could start. This is a CI workflow race, not an application bug.

Fix

Set free-disk-space: false for the up-features (ubuntu-latest) matrix entry so the background image-prune step no longer runs for this job. This job doesn't need the extra disk headroom badly enough to risk racing its own devcontainer builds.

Other free-disk-space: true matrix entries (provider, up-workspaces, up-handle-errors, up-provider-kubernetes) are unchanged.

[netlify]

✅ Deploy Preview for images-devsy-sh canceled.

Name	Link
🔨 Latest commit	cec5ebe
🔍 Latest deploy log	https://app.netlify.com/projects/images-devsy-sh/deploys/6a833f8366af8e0008565c21

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 6 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: f5d24665-31b3-47e1-adb8-abdbdfea23ac

📥 Commits

Reviewing files that changed from the base of the PR and between 2a06124 and cec5ebe.

📒 Files selected for processing (1)

• .github/workflows/pr-ci.yml

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}