8000 Tags · AIahmedshrf/twenty · GitHub
[go: up one dir, main page]

Skip to content

Tags

Tags

v1.17.4

Toggle v1.17.4's commit message
Fix 1.17 upgrade: build from source when built-function folder is mis…

…sing

v1.17.3 swallowed the error and skipped the function entirely,
meaning never-executed serverless functions were silently dropped
during migration.

Instead, when the built folder is missing, build the source
TypeScript on the fly using esbuild (same config used by
LogicFunctionResourceService) so the migration completes properly.

v1.20.11

Toggle v1.20.11's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: sync AI model catalog from models.dev (twentyhq#19426)

Automated daily sync of `ai-providers.json` from
[models.dev](https://models.dev).

This PR updates pricing, context windows, and model availability based
on the latest data.
New models meeting inclusion criteria (tool calling, pricing data,
context limits) are added automatically.
Deprecated models are detected based on cost-efficiency within the same
model family.

**Please review before merging** — verify no critical models were
incorrectly deprecated.

Co-authored-by: FelixMalfait <6399865+FelixMalfait@users.noreply.github.com>

v1.20.10

Toggle v1.20.10's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: IMAP skip no-select flag folders properly (twentyhq#19402)

Tested with a dovecot server running in Docker with synthetic seed

<img width="546" height="54" alt="image"
src="https://github.com/user-attachments/assets/81cbeae6-9cb6-406b-846a-209af403385f"
/>


/closes twentyhq#19090

v1.20.9

Toggle v1.20.9's commit message
fix(messaging): create messageThread.subject field metadata + column …

…in 1-21 backfill (twentyhq#19394)

- The 1-21 \`upgrade:1-21:backfill-message-thread-subject\` command
assumed the legacy \`sync-metadata\` flow would create the new
\`messageThread.subject\` field metadata and column on existing
workspaces. That sync was removed, so the column was never added and the
backfill silently skipped.
- The command now ensures the field exists by computing the standard
\`messageThread.subject\` flat field from the twenty-standard
application and running it through
\`WorkspaceMigrationValidateBuildAndRunService\` (same pattern used by
the page-layout / command-menu-item backfills). This creates both the
field metadata row and the workspace schema column.
- After ensuring the field, the existing \`UPDATE messageThread SET
subject = ...\` runs as before.

- [ ] On a workspace with no \`subject\` column on \`messageThread\`,
run \`yarn command:prod upgrade:1-21:backfill-message-thread-subject\`
and confirm:
  - the field metadata row is created in \`core.\"fieldMetadata\"\`
- the \`subject\` column is created on \`workspace_<id>.messageThread\`
  - existing message threads are backfilled from the most recent message
- [ ] Re-run on the same workspace and confirm it is a no-op (field
already exists, no rows to update)
- [ ] Run on a workspace that already has the column but \`NULL\`
subjects and confirm only the backfill runs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
0