AssegaiPHP upgrades

Upgrade Guide

Pick the versions and the parts of your stack you use. We will show the upgrade steps that apply to your app.

Tell us about your app

Choose your upgrade path

From version To version

How customized is your app?

Basic Medium Advanced

A fairly standard app using first-party defaults.

What does your app use?

I use ORM

Include ORM module wiring, repositories, and migrations.

I use Events

Include event wiring and listener checks.

I want OpenSwoole

Include OpenSwoole setup steps and caveats.

I use Windows

Include Windows notes where WSL2 or Linux is the safer path.

Release-line update

Release ready assegai update

Upgrade from 0.8.x to 0.9.0

0.9.0 raises the AssegaiPHP package line to PHP 8.4 and stabilizes the ORM around real SQL-family dialects, safer query construction, and clearer entity metadata.

Heads up. Upgrade your CLI first. The 0.9.x `assegai update` command is responsible for raising first-party package constraints before Composer resolves the new package set.

What `assegai update` should handle

Use PHP 8.4 or newer locally and in CI before running the update.
Upgrade the global or project-local CLI to the 0.9.x line.
Run `assegai update` from the project root.
The CLI updates `assegai.json` to the current default shape.
The CLI raises the root PHP constraint to the 0.9 baseline when it is older.
The CLI raises `assegaiphp/core`, detected ORM and Events integrations, and any already-required first-party 0.9 release-line packages to the current release line.
The CLI runs Composer with `--with-all-dependencies`, then replays installed package installers so package integrations can repair their module wiring.
If the workspace has a frontend package manager, the CLI refreshes frontend dependencies after the PHP package update.

What you still need to do

Confirm every deployment target, CI image, and local development environment runs PHP 8.4 or newer.
Commit or stash local application changes before upgrading so Composer and generated-file diffs are easy to review.
Review `composer.json` after `assegai update`, especially if the app pins first-party packages in unusual sections or custom aliases.
Re-run your application test suite after Composer finishes.

Before you call the upgrade done

Run `composer validate --strict`.
Run your project test suite.
Start the app locally with `assegai serve` and smoke test the main routes.

Helpful docs

Data and ORM Data Sources Entities Migrations Drivers

Looking ahead

Upcoming milestones

Only useful if you are planning more than one upgrade jump.

0.8.0

OpenSwoole Runtime Foundations

Long-lived runtime foundations, safer request scope, and an experimental OpenSwoole path.

0.9.0

ORM Stability Rewrite

Dialect-aware ORM stability across MySQL, MariaDB, SQLite, PostgreSQL, and MSSQL.

1.0.0

Confidence Release

Ship the minimum viable identity of AssegaiPHP in a polished form, with additional 0.x milestones if needed before then and larger expansion work landing in 1.0+.