Skip to main content

​
Alpha upgrade notes

​
0.1.0-alpha.1 → 0.1.0-alpha.2 (planned)

This is an upgrade preparation stub, not a release announcement or a claim that an alpha.1-to-alpha.2 production upgrade has been rehearsed. Alpha.2 is not published yet. The framework in this checkout adds these migrations after the 0029_runner_configuration migration in the alpha.1 tag: Read migrations, inspection views, and the support matrix before upgrading. Neki remains outside the launch support claim.
  1. Take and verify a restorable backup. Record the runtime version, actor_migrations rows, owned-table schema, and deployment configuration.
  2. Drain and stop all old runners for the initial alpha upgrade rehearsal. Start the candidate against a restored disposable copy first, using the same Postgres server version and permissions as the deployment.
  3. Let Actors.layer apply the framework migrations; apply your application migrations separately. With row-level security enabled, follow the view-owner procedure for new views before enabling traffic.
  4. Confirm readiness, an existing receipt replay, new commands, pending outbox/job recovery, and inspection with the production tenant role. Keep ingress paused until those checks pass.
There are no framework down migrations. A failed rehearsal is a stop, not permission to delete migration-history rows. A rollback after incompatible schema or placement changes requires the verified backup and the old runtime/configuration. Complete and record the actual upgrade rehearsal before promoting alpha.2; rolling mixed-alpha compatibility is not established by this stub.