compatibility

Align supported PHP, Composer, database, and CI version configurations across OrangeHRM environments.

1.1k|746|Updated Jan 5, 2017
One-click install
npx skills add https://github.com/orangehrm/orangehrm --skill compatibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compatibility
Source: https://github.com/orangehrm/orangehrm/tree/main/.agents/skills/compatibility
Command: npx skills add https://github.com/orangehrm/orangehrm --skill compatibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Misaligned version support specifications across OrangeHRM's PHP, database, frontend, CI, and deployment environments lead to installation failures, runtime errors, broken upgrade paths, and inconsistent documentation. Manually tracking all these surfaces to keep them aligned is error-prone and time-consuming.

Core Features & Use Cases

  • Cross-surface compatibility tracking: Covers PHP/Composer constraints, installer system requirements, CI test matrices, frontend build targets, Docker dev environment services, and packaging metadata.
  • Guided update workflows: Step-by-step instructions for safely adding or updating support for new PHP, database, browser, Node, or webserver versions without missing critical configuration files.
  • Use Case: A developer needs to add support for MySQL 8.0: this Skill guides them to update installer checks, CI test matrices, and dev environment configs in sync to avoid broken builds and failed installations.

Quick Start

Use the compatibility skill to list all current supported PHP versions for OrangeHRM and confirm they are consistent across composer.json, installer system requirements, and GitHub Actions workflows.

Frequently Asked Questions about compatibility

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

FAQPage Schema
How do I keep PHP and MySQL version constraints aligned across OrangeHRM environments?

To align PHP and MySQL version constraints across OrangeHRM environments, update composer dependency constraints, installer system requirement checks, CI test matrices, and Docker development configs simultaneously to prevent installation failures and runtime errors.

What causes OrangeHRM installation or upgrade failures when version specifications are mismatched?

Misaligned version support specifications across OrangeHRM's runtime, build, and deployment environments cause installation and upgrade failures due to inconsistent PHP, database, and webserver requirements in composer constraints, installer checks, and CI test matrices.

What's the best way to add support for a new database version in OrangeHRM without breaking builds?

The best way to add database version support in OrangeHRM is using guided update workflows to synchronize installer system requirement checks, GitHub Actions test matrices, and local development environment service versions to avoid broken builds and failed installations.

How do I check if my GitHub Actions test matrix matches OrangeHRM's supported PHP versions?

Check version consistency by listing current supported PHP versions for OrangeHRM and confirming they match across composer.json, installer system requirements, and GitHub Actions workflows to ensure CI test matrix alignment.

Do I need to update Node and frontend package metadata when changing OrangeHRM's build environment versions?

Yes, updating Node and frontend package metadata is required when changing OrangeHRM build environment versions to maintain cross-surface compatibility tracking across PHP, database, frontend, CI, and deployment configurations.

Why does OrangeHRM runtime fail after updating composer dependency constraints without updating installer checks?

OrangeHRM runtime fails because updating composer dependency constraints without synchronizing installer system requirement checks creates version misalignment, causing the installer to reject environments that the updated composer configuration actually supports.