PHPackages                             semitexa/update - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [DevOps & Deployment](/categories/devops)
4. /
5. semitexa/update

ActiveSemitexa-module[DevOps & Deployment](/categories/devops)

semitexa/update
===============

Semitexa Update — update lifecycle: package version detection, framework auto-deploy, remote bootstrap, and post-schema data patches

2026.05.12.0933(4w ago)117↓100%1MITPHPPHP ^8.4

Since Apr 23Pushed 4w agoCompare

[ Source](https://github.com/semitexa/semitexa-update)[ Packagist](https://packagist.org/packages/semitexa/update)[ RSS](/packages/semitexa-update/feed)WikiDiscussions master Synced 1w ago

READMEChangelogDependencies (3)Versions (12)Used By (1)

Semitexa Update
===============

[](#semitexa-update)

`semitexa/update` owns the **update lifecycle** of a Semitexa application — package version detection, plan building, ORM schema synchronization, and post-schema **data patches**. It is **not** a schema migration system.

Ownership boundary
------------------

[](#ownership-boundary)

LayerOwnerTools**Database schema** (tables, columns, indexes, foreign keys, safe-rename, deprecate-then-drop)`semitexa-orm``orm:diff`, `orm:sync`, `orm:status`**Update orchestration** (preflight, package version detection, sequencing)`semitexa-update``update`, `update:plan`, `update:status`, `update:packages:*`**Post-schema data patches** (backfills, normalizations, default-row creation)`semitexa-update``#[AsDataPatch]` + `update`**Developer tooling**`semitexa-dev``make:*`, `ai:*`, `dev-graph`A data patch must never issue DDL. Schema changes go through ORM. The runner enforces this with a DDL-keyword guard at apply time.

What this package does
----------------------

[](#what-this-package-does)

- discovers classes annotated with `#[AsDataPatch(...)]`
- runs phases in strict order: `pre`, `apply`, `post` — relative to the ORM schema sync
- resolves per-phase dependencies through a DAG
- stores `pending`, `applied`, and `failed` state in a per-database journal
- stops on the first failed patch and reports the failure

What this package does **not** do
---------------------------------

[](#what-this-package-does-not-do)

- it does **not** perform schema migrations — see `semitexa-orm`
- it does **not** create, alter, drop, rename, or truncate tables or columns
- it does **not** run inside `semitexa-dev` — Dev is for developer tooling only

Authoring a data patch
----------------------

[](#authoring-a-data-patch)

```