unoverse 0.1.175 → 0.1.176
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -116,13 +116,22 @@
|
|
|
116
116
|
# (scripts/lib/db-setup.sh). The old programmatic `require('./dist/db')` table
|
|
117
117
|
# setup is retired: the engine no longer ships a dist, and .sql migrations under
|
|
118
118
|
# apps/unoverse/engine/migrations are the single source of truth.
|
|
119
|
+
# --no-check-order, and it is NOT optional here: a database from before the
|
|
120
|
+
# 2026-07-28 squash has 002-018 recorded in pgmigrations with no matching files
|
|
121
|
+
# (they live inside 001_baseline now), so the order check refuses EVERY new
|
|
122
|
+
# migration with "Not run migration 019_… is preceding already run migration 002_…".
|
|
123
|
+
# db-setup.sh has carried this flag since the squash; this playbook runs the same
|
|
124
|
+
# command and did not, so `unoverse db-setup` worked while `unoverse deploy db`
|
|
125
|
+
# failed on the same database. Ordering still holds by filename and an applied name
|
|
126
|
+
# is never re-run, so the check buys nothing a squashed history can satisfy.
|
|
119
127
|
- name: "[4/5] Apply database migrations (node-pg-migrate)"
|
|
120
128
|
shell: |
|
|
121
129
|
docker compose exec -T -e NODE_TLS_REJECT_UNAUTHORIZED=0 unoverse \
|
|
122
130
|
npx node-pg-migrate up \
|
|
123
131
|
--migrations-dir /app/apps/unoverse/engine/migrations \
|
|
124
132
|
--migration-file-language sql \
|
|
125
|
-
--no-lock
|
|
133
|
+
--no-lock \
|
|
134
|
+
--no-check-order
|
|
126
135
|
args:
|
|
127
136
|
chdir: /opt/gravity
|
|
128
137
|
register: migrate_result
|
package/package.json
CHANGED