You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Compatibility with Laravel/framework breaks after version 13.35 #223
Describe the bug
Blaze works perfectly with laravel/framework v13.35, but upgrading to v13.36 and later breaks as the file names of the blade view cache files has changed.
v13.35 and prior it was f06d2bc9de9c5b90f9db0cbaaa716d49.php or similar
v13.36 and later it is f06d2bc9de9c5b90f9db0cbaaa716d49__7f20d220a25c950ba43f1353e57f9b30.php
The latter _7f20d220a25c950ba43f1353e57f9b30 part is the same for all view files.
Component causing the issue
laravel/framework, so all blade components
Activity
tallenglish commentedon Oct 19, 2026
reverting to v13.35 framework fixes the issue for now, but blaze likely needs a fix to check for v13.36+ version and use the new file names.
ghabriel25 commentedon Oct 19, 2026
Breaking change from laravel/framework#61822
ganyicz commentedon Oct 23, 2026
Thanks for reporting @tallenglish
This will be fixed in the next release