mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-11-16 17:09:09 +00:00
While this PR was open, merge train 2 merged 240_provider_node_custom_json_config.sql (#18353) and 241_seen_models.sql (#18359) into release/v3.8.54. With the series frozen at 239, the gate rejected both base files and the compatibility tests' synthetic 240 slot collided with the real one, so CI went red on the merge ref. A merged migration is never renamed, so the freeze moves to the highest old number on the base: LEGACY_MIGRATION_MAX is now 241, and its comment says to raise it in the same merge if another NNN_ file lands before this PR does. The tests no longer hard-code the free slot: the timestamp compatibility test takes the first old number above every real file, and the numbering tests derive the top and the number above it from LEGACY_MIGRATION_MAX. The pinned value test now pins 241. The database guide and the changelog fragment say 001-241, and the conversion recipe lists 237 to 241 as slots that always need a compatibility entry.