Uh oh!
There was an error while loading. Please reload this page.
Drop PHP 7.4 support - #7924
Conversation
78e041f to
1adc0f0CompareUh oh!
There was an error while loading. Please reload this page.
michalsn
commented
Sep 11, 2023
I don't know when v4.5 will be released, but currently, PHP 7.4 is still used by more than 20% of 4.4 users. https://packagist.org/packages/codeigniter4/framework/php-stats#4.4 |
kenjis
commented
Sep 11, 2023
The release of 4.5 will be after the release of PHP 8.3, no matter how soon. |
Uh oh!
There was an error while loading. Please reload this page.
kenjis
commented
Sep 13, 2023
auto-label failed. https://github.com/codeigniter4/CodeIgniter4/actions/runs/6167549712/job/16739374912 |
ddevsr
commented
Sep 13, 2023
@kenjis By https://github.com/prince-chrismc/label-merge-conflicts-action#faq---how-do-i-fix-resource-not-accessible-by-integration We already set minimum permission permissions:
issues: write
pull-requests: write |
datamweb
commented
Sep 13, 2023
I don't know, but isn't there a difference between |
ddevsr
commented
Sep 13, 2023
@datamweb I agree, Different : - uses: prince-chrismc/label-merge-conflicts-action@v3
with:
conflict_label_name: 'stale'
github_token: ${{ github.token }}uses: actions/checkout@v4
with:
repository: codeigniter4/api
token: ${{ secrets.ACCESS_TOKEN }}Parameter https://github.com/codeigniter4/CodeIgniter4/blob/develop/.github/workflows/deploy-apidocs.yml#L40 |
They are the same.
|
MGatner
commented
Sep 13, 2023
Any ideas on the other failure? I will try rerunning.
|
Upload coverage results to Coveralls / coveralls https://github.com/codeigniter4/CodeIgniter4/actions/runs/6167549719/job/16751771845?pr=7924 |
Created an issue #7941 |
172bffa to
76718a7CompareIt seems unethical to continue to support an unmaintained PHP version. If someone needs using PHP 7.4, s/he can use v4.4. |
michalsn
commented
Sep 17, 2023
Personally, I'm not against abandoning PHP 7.4. However, if we draw the line based on the officially supported version of PHP and not what our users actually use, then supporting PHP 8.0 after November 26, 2023, will also be "unethical". What's more... according to composer stats, the percentage of users using 8.0 is smaller than those using 7.4. If we want to say "Use CI 4.4 if you need support for an unsupported version of PHP," then it would be more natural to introduce PHP 8.1 as a minimum version for CI 4.5 release. |
kenjis
commented
Sep 19, 2023
I would like to merge this. |
Co-authored-by: MGatner <mgatner@icloud.com>
67f2aa6 to
83865aeComparekenjis
commented
Sep 23, 2023
No one objects, so I merge. |
MGatner
commented
Sep 27, 2023
I'm good with this. @michalsn I am generally in favor of keeping our supported versions in line with PHP, while also recognizing driving factors. Often time is just our biggest bottleneck - we haven't always been compatible with new versions of PHP on their release, which is a much higher priority. On the bottom end we are motivated to drop versions that prevent us from adopting features. The feature set of PHP 7.4 => 8 is way more enticing than 8.0 => 8.1, so while I agree it would be better to keep consistency there's also less motivation among all the work competing for priority. |
Description
See #6921
Supersedes #6922
Checklist: