Marie 4827ad600d Add workspace constraint on defaultRoleId and activationStatus (#11191) ...

Part of https://github.com/twentyhq/core-team-issues/issues/526

An active workspace's defaultRoleId should never be null.
We can't rely on a simple postgres NOT NULL constraint as defaultRoleId
will always be initially null when the workspace is first created since
the roles do not exist at that time.
Since a suspended workspace can be active again, we should maintain that
rule during the workspace suspension. The only moment defaultRoleId can
have a null value is during the onboarding. this pr enforces that

2025-03-26 14:43:13 +00:00

..

command

Refactored and improved seeds (#8695)

2024-12-24 14:44:52 +01:00

constants

Fix all broken CIs (#7439)

2024-10-05 00:23:23 +02:00

database

Add workspace constraint on defaultRoleId and activationStatus (#11191)

2025-03-26 14:43:13 +00:00

engine

Add workspace constraint on defaultRoleId and activationStatus (#11191)

2025-03-26 14:43:13 +00:00

filters

fix(auth): Improve error management with sso + fix microsoft saml (#9799)

2025-01-24 10:36:18 +01:00

modules

[permissions] Enable permissions V1 for all workspaces (#11172)

2025-03-26 12:51:34 +00:00

queue-worker

Improve snackbar and fix sentry (#7181)

2024-09-21 06:33:15 +02:00

utils

[REFACTOR] twenty-shared multi barrel and CJS/ESM build with preconstruct (#11083)

2025-03-22 19:16:06 +01:00

app.module.ts

Deprecate message queue type (#10040)

2025-02-06 16:06:54 +01:00

instrument.ts

Lingui working with NODE ENV=production again (#10067)

2025-02-07 10:05:07 +01:00

main.ts

refactor(server): rename PORT to NODE_PORT (#10193)

2025-02-14 10:03:58 +01:00