fix(migrations): add renamed migration compatibility for 056/073/077/101 - #12036
Merged
diegosouzapw merged 2 commits intoAug 30, 2026
Conversation
diegosouzapw
force-pushed
the
fix/migration-renumber-compat-056-073-077-101
branch
from
August 30, 2026 14:19
0620906 to
6a529e0
Compare
diegosouzapw
merged commit Aug 30, 2026
9b9ea88
into
diegosouzapw:release/v3.8.51
3 of 7 checks passed
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…101 (diegosouzapw#12036) Adiciona compatibilidade de renomeação de migração para 056/073/077/101. Teste próprio atualizado (7/7 verde no worktree combinado + isolado). Fiz cherry-pick só dos 2 commits reais da PR (o fix + o ajuste do teste) direto na tip atual: a branch original carregava 3 commits antigos de drift do ciclo (release-workflow/electron, já mergeados de outras formas) mais um commit de auto-resolução de merge seu, que juntos geravam conflito redundante contra `.github/workflows/electron-release.yml`. Nenhum conteúdo seu foi perdido — força-pushed a branch limpa (autoria preservada). Obrigado!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #12035
Summary
When a migration file is renamed between releases, existing databases can retain the old migration name in
_omniroute_migrations. On startup, OmniRoute detects these mismatches, logs CRITICAL warnings, and the provider management API returns500, making the dashboard show providers as “missing”.Change
Extend
RENAMED_MIGRATION_COMPATIBILITYinsrc/lib/db/migrationRunner/constants.tsto cover these entries:provider_default→mcp_accessibility_compressiondiscovery_results→per_model_token_limitsplugin_metrics→api_key_stream_default_modeproxy_pool_rotation→api_key_usage_limitsThis lets
reconcileRenumberedMigrations()rewrite stale entries automatically, removes the CRITICAL warning, and avoids downstream API failures.Verification
/api/providersto return 500./api/providersreturned 200.Issue
Closes #12035