Laravel 12.x Compatibility

[laravel-shift]

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 12.x.

Before merging, you need to:

• Checkout the l12-compatibility branch
• Review all comments for additional changes
• Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

Summary by CodeRabbit

• Chores
  • Updated dependency version constraints to expand compatibility with newer library versions and testing frameworks. These changes help ensure smoother integration with the latest ecosystem standards and contribute to overall system stability.

[laravel-shift]

ℹ️ Shift detected you do not have a CI workflow using GitHub Actions. If you would like, Shift can help you get started with the CI Generator. Although the Shift is paid, GitHub Actions is free and having a CI workflow will improve the stability and review process for your package.

[laravel-shift]

⚗️ Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.

To do so, temporarily add Shift's fork to the repositories property of your composer.json:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/laravel-ip-middleware.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:

{
    "require": {
        "orkhanahmadov/laravel-ip-middleware": "dev-l12-compatibility",
    }
}

Finally, run: composer update

[coderabbitai]

Walkthrough

The pull request updates the dependency version constraints in the composer.json file. The changes extend support in the require section for illuminate/contracts, illuminate/http, and illuminate/support to include ^12.0. In the require-dev section, the constraints for orchestra/testbench and phpunit/phpunit have been expanded to support newer versions. No changes have been made to public or exported entities.

Changes

File	Change Summary
composer.json	Modified version constraints in the require section (illuminate/contracts, illuminate/http, illuminate/support now support ^12.0) and in require-dev (added support for ^10.0 for orchestra/testbench and ^11.5.3 for phpunit/phpunit).

Possibly related PRs

• Added Laravel 11 support #10: Updates version constraints in the composer.json for similar dependencies, aligning changes made in this PR.

Poem

I'm a rabbit with hops so light,
Darting through code both day and night.
Dependencies updated, fresh and grand,
Version constraints now neatly planned.
With every nibble, I cheer with delight! 🐰✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 27fedd8 and 9b41fa9.

📒 Files selected for processing (1)

• composer.json (1 hunks)

🔇 Additional comments (2)

composer.json (2)

25-27: Expand Laravel Dependency Support for Illuminate Packages

The updated version constraints for "illuminate/contracts", "illuminate/http", and "illuminate/support" now include ^12.0 alongside prior versions. This expands the compatibility range for the middleware to support Laravel 12.x. Please ensure that there are adequate integration tests confirming that the middleware behaves as expected under Laravel 12.

---

30-31: Update Development Environment Dependencies for Laravel 12 Compatibility

The adjustments for "orchestra/testbench" (now including ^10.0) and "phpunit/phpunit" (including ^11.5.3) in the require-dev section help ensure that the testing framework supports the updated Laravel environment. Verify that the existing test suite runs smoothly with these new versions.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.