Repository navigation
fix(init): default compat to console 0.8+ and core-api 2.x - #15
Merged
Merged
Conversation
The scaffold defaulted to console >=0.7.0 <0.8.0 and core-api ^1.6, so a fresh extension was incompatible with every Laravel 12 instance (console 0.8.x, core-api 2.x) that registry v2 serves.
This was referenced Nov 19, 2026
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.
flb initwrotecompatas console>=0.7.0 <0.8.0and api^1.6. A freshly scaffolded extension was therefore incompatible with every Laravel 12 instance (console 0.8.x, core-api 2.x) that registry v2 serves.Found while setting up local e2e. The new defaults are console
>=0.8.0 <0.10.0and api^2.0;--consoleand--apistill override them.Tests:
npx vitest runpasses. The e2e script's compat assertion is updated to match.