Repository navigation
Conversation
Composer 2.11 no longer exempts versioned dev branches from advisory blocking, so a lockless install fails on Laravel 10, or quietly falls back to a much older fleetbase/core-api where the constraint allows it. Ignore only the advisories this dependency tree hits. on-audit false keeps them in composer audit. Remove at the Laravel 12.69+ upgrade.
The advisory published on 2026-11-04 leaves symfony/http-kernel 6.4.50 as the first patched 6.4 release, and it conflicts with var-dumper below 6.3. Without this, install fails or falls back to an old fleetbase/core-api.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #10 +/- ##
=========================================
Coverage 26.49% 26.49%
Complexity 643 643
=========================================
Files 19 19
Lines 2265 2265
=========================================
Hits 600 600
Misses 1665 1665
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
Author
|
Closing without merging. Laravel 12 replaces this stopgap: each repo's Laravel 12 release resolves Composer 2.11 with no advisory ignores, and the goal is zero exceptions. The branch is kept. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Composer 2.11 refuses Laravel 10 in repos without a lock file, which fails CI here on the next run.
illuminate/*tree hits toconfig.policy.advisories.ignore-idwithon-audit: false: they stop blocking, andcomposer auditstill reports them. Each reason names the Laravel 12.69+ upgrade as the point to remove it.symfony/var-dumperto^5.4.29|^6.2. The advisory published on 2026-11-04 leavessymfony/http-kernel6.4.50 as the first patched 6.4 release, and it conflicts with var-dumper below 6.3.This setting only applies when this repo is the Composer root, so it doesn't change what consumers install.
Test plan