@crynobone I think all theses change are breaking ones, because some Laravel 11.x applications may rely on theses behaviours. (Laravelshift for example deletes default files from the skeleton, which would mean the framework behaviour would kick in).

@Jubeki That's doesn't seem like the right approach. Furthermore, we probably need to be able to sync changes (via GitHub Actions) between multiple skeleton now with the introduction of multiple starter kit.

@crynobone but changing this still means, that applications, who do not define the value in their app config, fallback to the framework config (which was the intention). Meaning their application could possibly break in a minor version bump.

I also don't think that all values need to be synced completely between the skeleton and the framework. Changes to the defaults in the framework should only be allowed on major versions in my opinion.