Open
Description
This issue is automatically created based on existing pull request: #39882: Remove legacy compatibility code for PHP versions < 8.1
Description (*)
This pull request removes code that was designed to be ran on PHP <8.1.
Also, removed checks for PHP_VERSION_ID contact availability, since it's available in all PHP versions
Related Pull Requests
Fixed Issues (if relevant)
- Fixes magento/magento2#<issue_number>
Manual testing scenarios (*)
- ...
- ...
Questions or comments
Contribution checklist (*)
- Pull request has a meaningful description of its purposeAll commits are accompanied by meaningful commit messagesAll new or changed code is covered with unit/integration tests (if applicable)README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an updateAll automated tests passed successfully (all builds are green)
Metadata
Metadata
Assignees
Labels
USE ONLY for FRAMEWORK RELATED BUG!Gate 3 Passed. Manual verification of the issue completed. Issue is confirmedMay be fixed according to the position in the backlog.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branchIssue related to Developer Experience and needs help with Triage to Confirm or Reject it
Type
Projects
Status
Ready for Development
Milestone
Relationships
Participants
Activity
engcom-Dash commentedon Jun 18, 2025
@ihor-sviziev Thank you for the report & collaboration!
Looking at the PR changes we can confirm that for PHP version < 8.0.0 legacy code can be removed. PHP_VERSION_ID is available in all the PHP versions hence we can safely remove the checks for it. Also, T_NAME_QUALIFIED & T_NAME_FULLY_QUALIFIED are available in versions starting from 8.0.0.
Hence confirming the issue.
github-jira-sync-bot commentedon Jun 18, 2025
✅ Jira issue https://jira.corp.adobe.com/browse/AC-14971 is successfully created for this GitHub issue.
m2-assistant commentedon Jun 18, 2025
✅ Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.