Documentation / Project Config - Service Version Parity Transparency

[Romerolweb]

Link https://supabase.com/docs/guides/cli/local-development

Describe the problem When running supabase start, the CLI warns about version mismatches (e.g., Postgres 15.8 vs 17.6). While the CLI suggests running supabase link to update, there is no documentation explaining where these "official" versions are defined or how to manually pin them in `config.toml

or other options likemise` to ensure every developer on a team is using the exact same service versions.

• Describe the improvement Provide a "Service Versions" section in the documentation that explains:

• How Supabase selects the default image versions for local development.

• How to use the supabase/config.toml to explicitly lock these versions to avoid the "Different service versions" warning across a team.

Additional context Example warning from CLI:

WARNING: You are running different service versions locally than your linked project:
supabase/postgres:15.8.1.093 => supabase/postgres:17.6.1.072
supabase/storage-api:v1.33.5 => v1.33.0
Run supabase link to update them.