test: include php 8.4 and 8.5 for testing

[drwho725]

PR Type

Tests

---

Description

• Add PHP 8.4 and 8.5 to CI test matrix

• Expand testing coverage for newer PHP versions

---

Diagram Walkthrough

flowchart LR
  oldMatrix["PHP 7.4-8.3"] -- "add versions" --> newMatrix["PHP 7.4-8.5"]

Loading

File Walkthrough

	Relevant files
Tests	php.yml Extend PHP version test matrix                                                      .github/workflows/php.yml Extended php-versions matrix to include PHP 8.4 and 8.5 Maintains existing PHP versions 7.4, 8.0, 8.1, 8.2, 8.3 Enables CI testing against latest PHP releases +1/-1

---

[qodo-slickdeals]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
🟢	No codebase code duplication found No new components were introduced in the PR code
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-slickdeals]

PR Code Suggestions ✨

No code suggestions found for the PR.