Danny Kopping 85f56e4944 fix: recreate ai_provider_type instead of ADD VALUE (#25895) ...

Coder runs all migrations in a single transaction (`pgTxnDriver`).
Postgres forbids using an enum value added by `ALTER TYPE ... ADD VALUE`
within the same transaction that added it. Migration `000499` widened
`ai_provider_type` with `ADD VALUE`, and `000504` casts existing
`chat_providers` rows to that enum in the same transaction. On
deployments with a legacy provider using one of the new values (for
example `openai-compat`), the batch failed with `unsafe use of new
value` and the server could not start.

Recreate the type (create a new enum, alter the column, drop and rename)
instead of using `ADD VALUE`, matching the existing precedent in
`000144_user_status_dormant`. A freshly created enum's values are usable
immediately in the same transaction, so the cast in `000504` succeeds.
The resulting schema is identical, so `make gen` produces no `dump.sql`
diff and databases that already applied these migrations see no drift.

Added a regression test that seeds an `openai-compat` provider and
applies `000499` through `000504` in a single transaction, reproducing
the production path. The per-step `Stepper` used by the other migration
tests commits each migration separately and cannot surface this class of
bug.

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

---------

Signed-off-by: Danny Kopping <danny@coder.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-01 13:30:45 +00:00

..

docs

fix: recreate ai_provider_type instead of ADD VALUE (#25895)

2026-06-01 13:30:45 +00:00

scripts

fix: return 404 instead of 401 for missing OAuth2 apps (#18755)

2025-07-07 19:57:32 +02:00

skills

feat: add code-review skill and align workflow with doc-check (#21668)

2026-02-02 17:49:45 +00:00

settings.json

docs: add comprehensive development documentation (#18646)

2025-07-03 18:51:23 +02:00