[db.migrations] isn't a recognised key in config.toml

[texonidas]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

The schema application order outlined here, specifically the config.toml example, does not appear to be implemented.

To Reproduce

Add a [db.migrations] section to supabase/config.toml as outlined in the docs above, then attempt to generate a migration using db diff.

Expected behavior

A non-lexigraphical sort would be applied to the schemas.

Additional context

This just results in a failed to parse config error. After checking the config.toml documentation, I can see that this field isn't defined there. I'm not sure which segment of the docs is out of joint, but the functionality outlined doesn't appear to be available, as I couldn't find anything resembling this in any other section of the config.toml.

[silentworks]

You need to be using the latest version of the CLI for this to work. The latest version is 2.15.8. You can check your version by running supabase -v if you installed it with homebrew or npx supabase -v if you installed it with npx.

[texonidas]

In that case, do the config.toml docs need to be updated? There's no mention of this key here.

[sweatybridge]

closing as working as intended. we will automate updating of docs separately