Deploys only end up in legacy Galaxy infrastructure

Our app was automatically migrated to the newer Galaxy infrastructure over the weekend. I just got a notification that the app had been stopped and upon logging in I saw messages about DNS and my app being migrated.

Since this happened using my original deploy command which I’ve used for years doesn’t update the code any more. I can actually see it increment the build counter on the legacy Galaxy landing page, but I cannot get it to deploy to the newer infra. There aren’t even any build messages registered on the newer Galaxy with the command.

I updated the DNS, but that didn’t help. I’m deploying to Australia region.

Meteor version 3.4

I’ve tried to reach out to support but already 12 hours without an answer.