fix: exclude Astro docs/ from FOSSA license scanning#5499
Conversation
The docs/ Astro site was not excluded from FOSSA npm scanning, causing License Compliance to fail on PRs that touch docs/. The root packages are build-time only and not distributed with the Wails module: - sharp → @img/sharp-libvips-* (LGPL-3.0-or-later) - astro-d2 → @terrastruct/d2 (MPL-2.0) Extends the existing website/ exclusion pattern to also cover docs/.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughFOSSA license scanning configuration is updated to exclude the ChangesFOSSA Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Summary
The
docs/Astro site was not in.fossa.yml's exclusion list, causing FOSSA License Compliance to fail on any PR that touchesdocs/.Root cause:
.fossa.ymlcorrectly excludeswebsite/(Docusaurus), but the newerdocs/(Astro/Starlight) directory was not added when the docs site was migrated. FOSSA scansdocs/package-lock.jsonand flags two groups of build-only packages:@img/sharp-libvips-*(14 platform variants, fromsharp)LGPL-3.0-or-later@terrastruct/d2(fromastro-d2)MPL-2.0Neither is distributed with the Wails Go module or
@wailsio/runtime. Both are dev/build-time image and diagram tooling only.Fix: two-line addition to
.fossa.yml, mirroring the existingwebsite/exclusion.Test plan
docs/Summary by CodeRabbit