You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(run-ops): one RUN_OPS_* env var family, drop TASK_RUN_* aliases
The NEW-DB writer had two names (TASK_RUN_DATABASE_URL from the original split +
RUN_OPS_DATABASE_URL used by the schema/docker/.env), bridged by a `??` coalesce. Collapse
to a single canonical RUN_OPS_* family and delete the aliases (nothing deployed uses them yet):
- TASK_RUN_DATABASE_URL -> RUN_OPS_DATABASE_URL (the writer; the ?? and the
runOpsNewDatabaseUrl indirection are gone — consumers read env.RUN_OPS_DATABASE_URL directly)
- TASK_RUN_LEGACY_DATABASE_URL -> RUN_OPS_LEGACY_DATABASE_URL
- TASK_RUN_DATABASE_READ_REPLICA_URL -> RUN_OPS_DATABASE_READ_REPLICA_URL
- TASK_RUN_DATABASE_DIRECT_URL -> removed (dead; the schema no longer declares directUrl)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .server-changes/run-ops-auto-migrate.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,4 +3,4 @@ area: webapp
3
3
type: feature
4
4
---
5
5
6
-
Automatically migrate the dedicated run-ops database on deploy (entrypoint + `@internal/run-ops-database` deploy/status scripts) and resolve its connection through one canonical`RUN_OPS_DATABASE_URL`(falling back to `TASK_RUN_DATABASE_URL`) so migrations always target the DB the app connects to.
6
+
Automatically migrate the dedicated run-ops database on deploy (entrypoint + `@internal/run-ops-database` deploy/status scripts), and standardize the run-ops DB connection on a single`RUN_OPS_DATABASE_URL`family (dropping the `TASK_RUN_DATABASE_URL` aliases) so migrations always target the DB the app connects to.
0 commit comments