Skip to content

Conversation

@davedevelopment
Copy link
Member

Refs #85

There will be opportunities for further cleanup, but setting the requirements comes first.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR removes outdated PHP versions from the CI tests to drop support for PHP versions lower than 7.3.

  • Removed PHP versions 5.3 through 7.3 from the workflow matrix
  • Retained testing for PHP 7.4, 8.0, and 8.1
Files not reviewed (2)
  • .travis.yml: Language not supported
  • composer.json: Language not supported
Comments suppressed due to low confidence (1)

.github/workflows/tests.yml:8

  • The diff removes PHP 7.3 from the test matrix, but the PR title indicates dropping support for PHP versions lower than 7.3. If PHP 7.3 should be retained as supported, please remove the deletion of the '7.3' entry; otherwise, update the PR title and description to reflect its removal.
-          - '7.3'

@aik099 aik099 changed the title Drop support for PHP <7.3 Drop support for PHP <=7.3 Apr 29, 2025
Copy link
Member

@aik099 aik099 left a comment

Choose a reason for hiding this comment

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

I've updated your PR title (replaced <7.3 with <=7.3) as per Copilot review 😄 suggestions.

Otherwise, looks good.

@davedevelopment davedevelopment marked this pull request as ready for review April 29, 2025 13:10
@davedevelopment davedevelopment merged commit 06d9e99 into master Apr 29, 2025
12 checks passed
@davedevelopment
Copy link
Member Author

@aik099 what are your feelings on versioning with regards to dropping support for PHP versions and major or minor bumps? I really don't care either way, I see both sides of the arguments...

@aik099
Copy link
Member

aik099 commented Apr 29, 2025

Considering specifics of this project (assets are the same all the time and we're only fixing PHP version compatibility), then doing a 2.1.0 release would be enough.

I'm also fine with the 3.0.0 release.

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.

2 participants