Add OPCache configuration section to PHP 8.5.2 and update bundle release to 2026.1.30

[N6REJ]

PR Type

Enhancement

---

Description

• Add OPCache configuration section to PHP 8.5.2

• Configure opcache.enable and opcache.enable_cli settings

• Update bundle release version to 2026.1.30

---

Diagram Walkthrough

flowchart LR
  A["PHP 8.5.2 php.ini"] -- "Add opcache section" --> B["OPCache Configuration"]
  C["build.properties"] -- "Update version" --> D["Bundle Release 2026.1.30"]

Loading

File Walkthrough

Relevant files

Configuration changes

php.ini Add OPCache configuration section                                                bin/php8.5.2/php.ini Added new [opcache] configuration section Set opcache.enable = 0 to disable OPCache by default Set opcache.enable_cli = 0 to disable OPCache for CLI Added descriptive comments for each setting +7/-0      build.properties Update bundle release version                                                        build.properties Updated bundle.release from 2026.1.16 to 2026.1.30 +1/-1

---

[qodo-code-review]

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
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
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

Compliance status legend

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

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[github-actions]

🐘 PHP Module Tests - Results

Test Date: 2026-01-30 15:12:05 UTC
Status: ✅ All tests passed

📊 Test Results by Version

PHP 8.5.2

Results: 4 of 4 tests completed

All tests passed successfully! ✨

---

📋 Test Phases

Each version is tested through the following phases:

• Phase 1: Basic PHP Validation (Download, Extract, Verify Executable)
• Phase 2: Extension Validation (Download, Architecture Check, Loading Test)
• Phase 3: Dependency Validation (Download Dependencies, Test with Dependencies)
• Phase 4: Functional Testing (Test Extension Functionality)

Check artifacts for detailed logs.