Skip to content

# PHP Migration Library v6.0 #56

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

# PHP Migration Library v6.0 #56

wants to merge 5 commits into from

Conversation

byjg
Copy link
Owner

@byjg byjg commented Mar 25, 2025

This PR introduces version 6.0 of the PHP Migration library with several breaking changes to improve compatibility with modern PHP versions and dependencies.

Major Changes

  • Upgraded minimum PHP version requirement to PHP 8.1
  • Updated anydataset-db dependency to version 6.0
  • Improved compatibility with PHP 8.x versions

Breaking Changes

Component Change Impact
PHP Version Minimum version increased to PHP 8.1 Applications running on PHP < 8.1 will need to upgrade
Dependencies anydataset-db upgraded to v6.0 Projects need to ensure compatibility with anydataset-db v6.0

Requirements

  • PHP 8.1 or higher (supports up to PHP 8.4)
  • PDO extension
  • Compatible with anydataset-db ^6.0

Supported Databases

  • SQLite
  • MySQL
  • SQL Server
  • PostgreSQL

Please ensure your application meets these requirements before upgrading to this version.

Description by Korbit AI

What change is being made?

Update the PHP migration library to version 6.0, by introducing support for PHP 8.4, refactoring code for improved database handling, updating dependencies, enhancing documentation, simplifying test configurations, and removing deprecated schedule elements from CI workflow.

Why are these changes being made?

The major version update aligns the library with the latest PHP versions and modern practices, enhancing maintainability and usability. Refactoring improves code clarity by centralizing database name retrieval and Uri handling, while updated documentation provides clearer guidance for new users. Removal of deprecated settings from the CI workflow adheres to the latest standards, ensuring the build system is more streamlined and efficient.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Copy link

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

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

Review by Korbit AI

Korbit automatically attempts to detect when you fix issues in new commits.
Category Issue Fix Detected
Readability Redundant Union Type ▹ view
Files scanned
File Path Reviewed
src/Database/MySqlDatabase.php
src/Database/PgsqlDatabase.php
src/Database/DblibDatabase.php
src/Database/AbstractDatabase.php

Explore our documentation to understand the languages and file types we support and the files we ignore.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • On any given comment that Korbit raises on your pull request, you can have a discussion with Korbit by replying to the comment.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Documentation
Logging
Error Handling
Readability
Design
Performance
Security
Functionality

Feedback and Support

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here

@@ -16,19 +16,13 @@ public static function schema(): string
return 'pgsql';
}

public static function prepareEnvironment(UriInterface $uri): void
public static function prepareEnvironment(UriInterface|Uri $uri): void
Copy link

Choose a reason for hiding this comment

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

Redundant Union Type category Readability

Tell me more
What is the issue?

The union type hint 'UriInterface|Uri' is confusing since Uri implements UriInterface, making the union type redundant.

Why this matters

Redundant type hints make code harder to understand and can confuse developers about which interface or class should be used.

Suggested change ∙ Feature Preview
public static function prepareEnvironment(UriInterface $uri): void
Provide feedback to improve future suggestions

Nice Catch Incorrect Not in Scope Not in coding standard Other

💬 Looking for more details? Reply to this comment to chat with Korbit.

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