Guard `yarn database:migrate:prod` (#19008)

## Motivations
A lot of self hosters hands up using the `yarn database:migrated:prod`
either manually or through AI assisted debug while they try to upgrade
an instance while their workspace is still blocked in a previous one
Leading to their whole database permanent corruption

## What happened
Replaced the direct call the the typeorm cli to a command calling it
programmatically, adding a layer of security in case a workspace seems
to be blocked in a previous version than the one just before the one
being installed ( e.g 1.0 when you try to upgrade from 1.1 to 1.2 )

For our cloud we still need a way to bypass this security explaining the
-f flag

## Remark
Centralized this logic and refactored creating new services
`WorkspaceVersionService` and `CoreEngineVersionService` that will
become useful for the upcoming upgrade refactor

Related to https://github.com/twentyhq/twenty-infra/pull/529

This commit is contained in:

Paul Rastoin

2026-03-27 15:39:18 +01:00

committed by

GitHub

parent c96c034908

commit 281bb6d783

25 changed files with 401 additions and 216 deletions

									
										packages/twenty-server/src/engine/constants/upgrade-command-supported-versions.constant.ts
									
		+10
		
												View File
												
				@@ -0,0 +1,10 @@

				export const UPGRADE_COMMAND_SUPPORTED_VERSIONS = [

				  '1.16.0',

				  '1.17.0',

				  '1.18.0',

				  '1.19.0',

				  '1.20.0',

				] as const;

				export type UpgradeCommandVersion =

				  (typeof UPGRADE_COMMAND_SUPPORTED_VERSIONS)[number];

Guard yarn database:migrate:prod (#19008)

Guard `yarn database:migrate:prod` (#19008)