Repository navigation
Tags
Tags
fix(messaging): split thread create/update statements and stop clobbe… …ring accumulator Fixes two bugs in MessagingMessageService.saveMessagesWithinTransaction. 1. Postgres "ON CONFLICT DO UPDATE command cannot affect row a second time" during message import: creates and subject updates were merged into a single bulk upsert keyed on id, so when the same thread id appeared in both lists Postgres rejected the statement. Issue them as two separate statements instead — insert for creates, upsert for subject updates — which is also closer to the pre-twentyhq#19351 behavior. 2. enrichMessageAccumulatorWithExistingMessageChannelMessageAssociations replaced the accumulator object wholesale, dropping any existingThreadInDB previously set by enrichMessageAccumulatorWithExistingMessageThreadIds. Mutate the existing accumulator instead.
chore: remove registeredCoreMigration (twentyhq#19376) Co-authored-by: Félix Malfait <felix.malfait@gmail.com>
Improve apps (twentyhq#19256) - simplify the base application template - remove --exhaustive option and replace by a --example option like in next.js https://nextjs.org/docs/app/api-reference/cli - Fix some bugs and logs - add a post-card app in twenty-apps/examples/
i18n - docs translations (twentyhq#19251) Created by Github action Co-authored-by: github-actions <github-actions@twenty.com>
Fix: composite update events not received (twentyhq#19053) Database batch events (update / insert / soft-delete / hard-delete) were building recordsBefore / recordsAfter after formatResult ran twice: once inside WorkspaceSelectQueryBuilder.getMany() / getOne(), and again in the CUD query builders. On the second pass, already-shaped composite fields (e.g. emails) went through formatFieldMetadataValue and kept the same object references as the live TypeORM row, so recordsBefore could change when the entity was updated—breaking workflow triggers and diffs.