Skip to content

Engineering standards

How Pharaonic packages are versioned, tested, released and supported. Everything here can be checked in the packages' repositories on GitHub.

Supported versions

  • Laravel packages have a line per Laravel major they support, named after it (11.x, 12.x, 13.x). Each line requires exactly the PHP versions its Laravel major supports, for example PHP 8.3 – 8.5 on 13.x. Some packages start at a later line, when they need a newer PHP feature.
  • PHP packages have a line per PHP minor, 8.0.x to 8.5.x. Each requires that PHP minor only.
  • Livewire packages have a line per Livewire major.
  • The newest PHP version any line supports is 8.5.

Each package's page in the catalog lists its lines and what each one requires, read from that line's latest release.

Fixes and support

  • A bug fix is made on the oldest affected line and ported to every later line, so all lines of a package carry the same fix.
  • Which versions receive security fixes is stated in each repository's SECURITY.md; read it for the package you use.
  • A line whose Laravel or PHP version no longer gets security fixes upstream is labelled on its documentation and in the package's compatibility table.

Testing

  • Every change runs in GitHub Actions on every PHP version the line supports, with both the lowest and the highest dependencies Composer allows.
  • composer check runs the same steps locally: code style (Pint), static analysis (PHPStan) and the test suite (Pest, or PHPUnit on lines that can't run Pest). Laravel and Livewire packages also validate composer.json and run composer audit.
  • Dependabot proposes Composer and GitHub Actions updates every week.

Versions and releases

  • Laravel and Livewire packages follow semantic versioning within each line: 13.1.0 adds features, 13.1.1 fixes them.
  • PHP packages' versions start with their PHP minor (8.5.2); releases on a line move the last number.
  • A release is a tag with a GitHub release whose notes come from the line's CHANGELOG.md (Keep a Changelog), then published on Packagist.

Deprecations and breaking changes

  • An existing line never breaks. A renamed or replaced API keeps the old name as a deprecated alias on every line.
  • Deprecated API is removed only in a new line (a new Laravel major's line, or a new PHP minor's line), and that line's changelog lists each removal with how to migrate.

Reporting a vulnerability

Please don't report security issues in public issues, discussions or pull requests. Use the package repository's Security tab → Report a vulnerability where it's available, or the private contacts in security.txt and on the contact page. Reports are reviewed by the maintainer, and a fix is released before the issue is disclosed, with credit unless you'd rather stay anonymous.

Maintainers and response

Pharaonic is maintained by Moamen Eltouny (Raggi), with contributors credited on each package. It's volunteer work, so there's no guaranteed response time; GitHub issues and pull requests are where work is tracked and answered.

Not in place yet

  • Published end-of-life dates for older lines.
  • Private vulnerability reporting on every repository: it's on for 23 of 29 package repositories. Where the Security tab has no Report a vulnerability button, use security.txt or the contact page.