@diagonal-hq/workflows 0.10.5 → 0.10.6
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.
- package/README.md +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -55,7 +55,7 @@ export default defineWorkflow(
|
|
|
55
55
|
|
|
56
56
|
A migration with `export const config` or `title` still builds, with a warning.
|
|
57
57
|
|
|
58
|
-
Create a file with `diagonal make:migration <name
|
|
58
|
+
Create a file with `npx diagonal make:migration <name>`. It creates `migrations/YYYYMMDDHHmmss_name.ts`. Deployment activation queues all new filenames independently as ordinary asynchronous workflows. They can run concurrently. The timestamp sorts filenames for listing and history and does not enforce execution order. Put dependent operations in one script. The platform records the filename for the workspace environment in Postgres before launch. It records every terminal outcome and never launches that filename again. Manual and nested workflow calls cannot run migration files. Inspect the existing workflow execution status for a failure, then add a new migration file to correct it.
|
|
59
59
|
|
|
60
60
|
Migrations run after schema activation. Existing schema safety guards still apply. Deploy a new field as optional, fill it in a migration, then make it required in a later release. A failed migration can leave completed writes in place, so account for those writes in the correction.
|
|
61
61
|
|
package/package.json
CHANGED