Skip to content

Add Laravel 13 support#11

Merged
alies-dev merged 1 commit intomainfrom
l13
Mar 6, 2026
Merged

Add Laravel 13 support#11
alies-dev merged 1 commit intomainfrom
l13

Conversation

@alies-dev
Copy link
Member

Summary

  • Update minimum PHP version to ^8.3
  • Add orchestra/testbench-core ^10.0 || ^11.0 for Laravel 12/13 support
  • Update CI matrix: PHP 8.3/8.4, Laravel 11/12/13
  • Drop PHP 8.2 and Laravel 10 from CI matrix

Existing Laravel 11+ support is preserved.

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on updating the project's dependencies to introduce support for Laravel 13. This involves adjusting the minimum PHP version requirement and broadening the range of supported orchestra/testbench-core versions, ensuring continued compatibility with the latest Laravel ecosystem.

Highlights

  • PHP Version Update: The minimum required PHP version has been elevated from ^8.2 to ^8.3 to align with newer Laravel versions.
  • Laravel 12/13 Support: The orchestra/testbench-core development dependency now includes support for ^10.0 and ^11.0, enabling compatibility with Laravel 12 and 13.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • composer.json
    • Updated the minimum PHP requirement from ^8.2 to ^8.3.
    • Expanded the orchestra/testbench-core development dependency to include versions ^10.0 and ^11.0.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/run-tests.yml
Activity
  • No specific activity has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates dependencies to add support for Laravel 13. The changes are a good step forward. I have one suggestion for the orchestra/testbench-core dependency to better reflect the dropping of Laravel 10 support, as mentioned in the pull request description. More critically, for full Laravel 13 compatibility, the laravel/nova dependency constraint (^4.25 || ^5.0) will likely need to be updated, as it currently does not appear to support Laravel 13. Since this is on a line not modified in this pull request, I am mentioning it here as it could be a blocker for the PR's stated goal.

Note: Security Review has been skipped due to the limited scope of the PR.

"require-dev": {
"interaction-design-foundation/coding-standard": "^0.3.0",
"orchestra/testbench-core": "^8.0 || ^9.0",
"orchestra/testbench-core": "^8.0 || ^9.0 || ^10.0 || ^11.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The PR description mentions that Laravel 10 is being dropped from the CI matrix. To align with this change and make the supported versions clearer, it would be best to remove the version constraint for orchestra/testbench-core that corresponds to Laravel 10 (^8.0). This helps to avoid confusion and makes it explicit that Laravel 10 is no longer a supported environment for development and testing.

Suggested change
"orchestra/testbench-core": "^8.0 || ^9.0 || ^10.0 || ^11.0",
"orchestra/testbench-core": "^9.0 || ^10.0 || ^11.0",

@alies-dev alies-dev merged commit 5474dfa into main Mar 6, 2026
0 of 12 checks passed
@alies-dev alies-dev deleted the l13 branch March 6, 2026 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant