|
| 1 | +# Upgrading to Runtime 0.2.0 |
| 2 | + |
| 3 | +Version 0.2.0 adds production diagnostics, deployment drift checks, download pins |
| 4 | +and crash recovery. PHP 8.5+, Composer 2.10.3+ and the reviewed Composer library |
| 5 | +line remain required. Read the [changelog](../../CHANGELOG.md) for the full list. |
| 6 | + |
| 7 | +## Update the package and command paths |
| 8 | + |
| 9 | +Change shell scripts and CI jobs from `vendor/bin/sympress-runtime` to |
| 10 | +`vendor/bin/runtime`. The old executable is no longer shipped. Composer commands |
| 11 | +such as `composer sympress-runtime` and configuration keys keep their names. |
| 12 | + |
| 13 | +Update in your development or build environment, review the resulting lockfile |
| 14 | +and generated files, then deploy that reviewed build: |
| 15 | + |
| 16 | +```sh |
| 17 | +composer require sympress/runtime:0.2.0 --no-plugins --no-scripts |
| 18 | +composer install --no-interaction |
| 19 | +vendor/bin/runtime validate |
| 20 | +vendor/bin/runtime --no-interaction |
| 21 | +``` |
| 22 | + |
| 23 | +If deployment uses a prebuilt environment dump, rebuild it for the intended |
| 24 | +environment before deployment. Do not distribute a development dump to production. |
| 25 | +Keep the referenced `var/runtime` payload with the generated configuration as |
| 26 | +described in [Deployment](../deployment.md). |
| 27 | + |
| 28 | +## Review native defaults |
| 29 | + |
| 30 | +- Environment caching defaults to `auto` and invalidates on source path, size or |
| 31 | + modification-time changes. Production dumps remain immutable until rebuilt. |
| 32 | +- `composer-managed: auto` disables dashboard file modifications and automatic |
| 33 | + updates in staging/production through the generated section. Existing constants |
| 34 | + take precedence; explicitly configure `false` if updates are managed elsewhere. |
| 35 | +- Native URL downloads create `sympress-runtime.lock`. Review and commit it, and |
| 36 | + use `--update-lock` deliberately when changing downloaded artifacts. |
| 37 | +- Native `db-check: health` no longer scans every table during setup. Schedule |
| 38 | + `vendor/bin/runtime doctor --database-health` explicitly; `--quick` is available. |
| 39 | +- Doctor requires explicit `WP_HOME` in staging/production. Its production profile |
| 40 | + requires HTTPS and reports opaque bootstrap code or unproven permissions as |
| 41 | + unknown, rather than certifying them. |
| 42 | + |
| 43 | +Compatibility profiles retain their documented defaults. The generated-file mode |
| 44 | +still defaults to `0600`; use `generated-file-mode: "0640"` with appropriate group |
| 45 | +ownership when deployment and PHP run as different users. |
| 46 | + |
| 47 | +## Establish deployment checks |
| 48 | + |
| 49 | +Run setup successfully before using `--check` or `--dry-run`: drift detection needs |
| 50 | +the generated baseline. Custom setup side effects can produce an unknown result. |
| 51 | +Use [production operations](../operations.md) for deployment gates, typed required |
| 52 | +variables, mounted secrets, names-only environment comparison and pruning. |
| 53 | + |
| 54 | +Interrupted supported package moves now recover through a private journal. |
| 55 | +Keep pending journals and owned backups intact until recovery completes. Pruning |
| 56 | +retains active payloads and refuses unknown ownership or pending recovery state. |
| 57 | +The supported layout boundaries remain documented in [Deployment](../deployment.md). |
0 commit comments