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.

Runtime update

Experimental runtime release assegai update

Upgrade from 0.7.6 to 0.8.0

0.8.0 adds OpenSwoole runtime foundations, safer long-lived request handling, and better package-driven repair through `assegai update`, while keeping the default PHP runtime as the normal path.

Heads up. OpenSwoole remains experimental in 0.8.0. If the tag is not out yet, treat this guide as release-prep guidance too.

What `assegai update` should handle

Run `assegai update` from the project root.
Let the CLI update `assegai.json` and `composer.json` to the current defaults where applicable.
Let the update command replay installed package installers so existing `orm` and `events` integrations are repaired automatically where possible.
If the workspace has a frontend package manager, let the update flow refresh those dependencies too.

What you still need to do

If your bootstrap still depends on the current working directory, switch it to `AssegaiFactory::createFromProject(AppModule::class, __DIR__)`.
If you are not evaluating OpenSwoole, stay on the default PHP runtime. `0.8.0` does not require a runtime switch.
Read the OpenSwoole runtime guide before enabling the runtime outside local experiments.
Re-run your test suite and confirm the default PHP runtime is green before switching the dev server runtime.

Before you call the upgrade done

Start the app with `assegai serve` and confirm normal PHP runtime behavior first.
Smoke test `/docs`, OpenAPI export, or Postman export if the app has a large or deeply nested module tree.
Check that package-driven integrations such as `OrmModule` and `EventsModule` are present in the root module after the update.

Helpful docs

Serving with OpenSwoole OpenSwoole Runtime API Docs and Clients

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

MySQL hardening first, then SQLite and PostgreSQL support with a dialect-aware query layer.

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+.