chore: allow laravel 13 (testbench ^11) and cover it in CI - #7
Merged
Conversation
Constraint widening only; no code changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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.
Part of the Laravel 13 readiness sweep across visualbuilder packages (neurobox NB-2860 groundwork).
Constraint widening only — no behaviour changes. Suite verified locally on laravel/framework v13.19.0: 29 passed (against the versionable chore/laravel-13-support branch aliased as 1.1.0). Note: the CI 13.* leg needs visualbuilder/versionable released with Laravel 13 support first (its PR: visualbuilder/versionable#1).
🤖 Generated with Claude Code