Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update composer.json for laravel 11 #30

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gyaaniguy
Copy link

@gyaaniguy gyaaniguy commented Jan 1, 2025

Hi

This package works great with laravel 11 and php 8.3 !
This PR updates composer.json

hth

Summary by CodeRabbit

  • Compatibility
    • Added support for PHP 8.3
    • Added compatibility with Laravel framework version 11

Copy link

coderabbitai bot commented Jan 1, 2025

Walkthrough

The pull request updates the composer.json file to expand compatibility with newer PHP and Laravel framework versions. The changes specifically add support for PHP 8.3 and Laravel 11, broadening the range of supported versions for the project's core dependencies. This update allows developers to use the latest versions of PHP and Laravel while maintaining backward compatibility with previous versions.

Changes

File Change Summary
composer.json Updated PHP version support from 7.2-8.2 to 7.2-8.3
composer.json Updated Laravel framework version support from ~5.1-10 to ~5.1-11

Poem

🐰 Composer's dance, versions expand!
PHP 8.3 joins the grand band
Laravel 11 takes the stage
Compatibility turns a new page
Rabbit hops with coding glee 🚀


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
🪧 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🔭 Outside diff range comments (1)
composer.json (1)

Line range hint 33-34: Update development dependencies for Laravel 11 compatibility

The development dependencies are outdated and might not support newer Laravel/PHP versions:

  • orchestra/testbench ~3.0 is very old
  • mockery/mockery ^0.9.9 is outdated

Consider updating to:

  "require-dev": {
-   "orchestra/testbench": "~3.0",
-   "mockery/mockery": "^0.9.9"
+   "orchestra/testbench": "^8.0",
+   "mockery/mockery": "^1.6"
  },
🧹 Nitpick comments (1)
composer.json (1)

25-25: Consider updating minimum PHP version requirements

While adding PHP 8.3 support is good, maintaining compatibility with PHP versions below 8.1 might pose security risks as they're no longer supported. Additionally, Laravel 11 requires PHP 8.2+, so the lower bounds could be raised.

Consider updating the PHP version constraint to:

-"php": "7.2.*|7.3.*|7.4.*|8.0.*|8.1.*|8.2.*|8.3.*",
+"php": "^8.2",
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 21571ea and cc50914.

📒 Files selected for processing (1)
  • composer.json (1 hunks)
🔇 Additional comments (1)
composer.json (1)

26-26: Verify Laravel version compatibility range

The extremely wide Laravel version range (5.1 through 11) raises some concerns:

  1. Laravel 11 is not yet released (expected Q1 2024)
  2. Supporting such a wide range of versions might lead to compatibility issues

Please verify:

  1. That the package features work correctly across all supported versions
  2. Consider using semantic versioning with a more focused range
✅ Verification successful

Let me check the actual usage of Laravel-specific features to better understand the compatibility requirements.


Wide Laravel version range is acceptable for this package

After analyzing the codebase, I can confirm that the wide Laravel version range (5.1 through 11) is acceptable because:

  1. The package has minimal Laravel dependencies, only using basic service provider functionality (mergeConfigFrom and publishes) which has remained stable across Laravel versions
  2. The core functionality (video streaming) relies on PHP's native functions (fopen, filesize, header) rather than Laravel-specific features
  3. No usage of version-sensitive Laravel components like Eloquent, Request handling, or Authentication is found

The package's simplicity and focus on PHP native functions makes it highly compatible across Laravel versions. The early inclusion of Laravel 11 is also acceptable as the package doesn't use any features that would be affected by the new version.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for potential breaking changes in Laravel versions
# Look for Laravel-specific method calls that might have changed across versions
rg -l "(?i)(response|request|config|route|view|auth|session|cache|storage|file|db|schema|artisan)" src/

# Check test suite compatibility
cat tests/TestCase.php

Length of output: 229


Script:

#!/bin/bash
# Check Laravel-specific features usage in the codebase
rg -A 3 "(?i)(response|request|config|route|view|auth|session|cache|storage|file|db|schema|artisan)" src/

# Check composer.json for package details and description
cat composer.json

Length of output: 3876

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