fix: short-syntax env_file is optional, not required - #77
Conversation
A string-form env_file (the overwhelmingly common case) was marked required: true, so any project whose env file is missing — a gitignored .env in a fresh clone, mastodon .env.production — hard-errored with an I/O error. docker compose config exits 0 with a "not found" notice; the analyzer now mirrors that: missing short-syntax env files are skipped and reported as info [env-file-missing] (surfaced via new ServiceReport.diagnostics through the audit). Long syntax with required: true still errors. Verified against Docker on the real mastodon compose: both succeed. 136 tests green.
|
Warning Review limit reached
Next review available in: 32 minutes 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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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. Comment |
The short-syntax env_file optionality fix (mastodon-class hard errors on gitignored .env files) shipped without a changelog entry; added to the 1.12.0 Fixed section.
Bug
String-form
env_file:was normalized torequired: true, so a missing env file — the gitignored.envin a fresh clone, or mastodon.env.production— produced a hard I/O error.docker compose configtreats it as a notice and exits 0 (verified against Docker).Fix
info [env-file-missing]ServiceReport.diagnosticsadded (JSON additive) and surfaced through the audit{path, required: true}still errors as beforeVerification