compatibility

Aligns supported PHP, database, Node, browser, and webserver versions across OrangeHRM source files.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/snow-gift111/orangehrm-ai-sdlc-capstone --skill compatibility-snow-gift111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compatibility
Source: https://github.com/snow-gift111/orangehrm-ai-sdlc-capstone/tree/main/.agents/skills/compatibility
Command: npx skills add https://github.com/snow-gift111/orangehrm-ai-sdlc-capstone --skill compatibility-snow-gift111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? OrangeHRM's supported-version claims are spread across Composer constraints, installer system checks, CI matrices, package.json files, and Docker dev environments, so version changes easily drift out of sync. This Skill guides you to inspect the actual source-of-truth files and keep every compatibility surface aligned. ## Core Features & Use Cases - Source-of-truth inspection: Maps each compatibility surface (PHP, MySQL/MariaDB, webserver, browser, Node/Yarn) to the exact files that own it, such as src/composer.json and installer/config/system_requirements.php. - Change workflows: Provides step-by-step procedures for changing PHP, database, browser/Node, or webserver support, including CI matrix and Docker dev-environment checks. - Review checklist: Ensures Composer constraints, installer checks, CI matrices, and packaging claims agree before shipping. - Use Case: When bumping the minimum PHP version, use this Skill to update Composer constraints, installer requirements, GitHub Actions matrices, and dev-environment containers consistently. ## Quick Start Ask the agent to check which PHP and MySQL versions OrangeHRM currently supports and verify that composer.json, the installer requirements, and CI workflows all agree.

Frequently Asked Questions about compatibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change the supported PHP version in OrangeHRM?

Read src/composer.json and devTools/core/composer.json for constraints, then update installer/config/system_requirements.php and the GitHub Actions PHP matrices. Resolve Composer dependencies on the lowest supported PHP version and verify the Docker dev environment provides the needed container.

How do I check which MySQL or MariaDB versions OrangeHRM supports?

Inspect installer/config/system_requirements.php for the installer's database checks and review the CI workflow database matrices for tested versions. Also check the Docker dev-environment database services and validate fresh install, upgrade, and PHPUnit coverage on affected engines.

Where are OrangeHRM browser and Node version requirements defined?

Check the package.json files in src/client, installer/client, and src/test/functional for packageManager, engines, and dependencies. Also look for .browserslistrc, Babel, Vue CLI, and Cypress config, plus CI jobs for frontend builds and tests.

Why should version numbers not be hardcoded in agent documentation?

Compatibility truth lives in owning files like composer.json and system_requirements.php, which change over time. Hardcoded copies in docs drift out of sync, so the Skill requires reading the source files before answering any supported-version question.

What must be validated when changing webserver or packaging support?

Read installer/config/system_requirements.php for installer-visible webserver requirements and inspect Docker/cloud packaging sources if distributed images are affected. Update public docs or release notes only after runtime checks, CI, and packaging claims line up.