Cannot push config after CLI upgrade

[AvaPL]

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

After I upgraded the Supabase CLI from 2.98.2 to 2.107.0, my supabase config push started failing with the following error:

cannot push config: a [remotes.*] block targets project abc123, which config push does not yet support. Remove the matching [remotes.*] block, or run config push from a config without it.

Of course, abc123 is not my real project ID.

To Reproduce

Not sure, my config is relatively simple and nothing has changed since I upgraded the CLI.

project_id = "local"

[remotes.production]
project_id = "abc123"

...

[remotes.production.auth.email.smtp]
enabled = true
...

Expected behavior

Config is pushed without an error, like it did in the previous version.

System information

• OS: macOS
• Version of Supabase CLI: 2.107.0

[coderabbitai]

🔗 Related PRs

supabase/supabase#47098 - Changed order that CLI flags are applied in [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Hallidayo]

Transferred from supabase/supabase repo

[7ttp]

I think a fix has already landed here:

• fix(cli): merge matching [remotes.*] block on config push #5618

will be out in the next release...

[AvaPL]

Thank you very much! I believe you can close this issue. I wasn't aware that there's a separate repository for the CLI, and didn't find this PR before opening the issue.