Upgrading studio to v3 and encountering hostname issue

This is likely a configuration file issue that can be easily resolved! When upgrading from Studio v2 to v3, the hostname prompt during deployment typically appears when your sanity.cli.js (or sanity.cli.ts) file is missing the studioHost property.

In Studio v3, the studioHost configuration was introduced to specify the hostname for your Studio deployment. If this property isn't present in your CLI config file, the deployment process will prompt you for it.

The good news: You don't need to change your existing hostname! You can keep using the same one you've been using.

To fix this without being prompted:

Add the studioHost property to your sanity.cli.js or sanity.cli.ts file:

import { defineCliConfig } from 'sanity/cli'

export default defineCliConfig({
  api: {
    projectId: 'your-project-id',
    dataset: 'your-dataset'
  },
  studioHost: 'your-existing-hostname' // Add this line
})

Or if you're using environment variables:

import { defineCliConfig } from 'sanity/cli'

export default defineCliConfig({
  api: {
    projectId: process.env.SANITY_STUDIO_PROJECT_ID,
    dataset: process.env.SANITY_STUDIO_DATASET
  },
  studioHost: process.env.SANITY_STUDIO_HOSTNAME
})

Your existing hostname is the subdomain part of your current Studio URL (if your Studio is at my-studio.sanity.studio, the hostname is my-studio).

Why this might be different from your other upgrades: It's possible that your other Studios already had this configuration added (perhaps they were upgraded earlier or had different initial setups), or you may have provided the hostname during those deployments and it was cached.

Once you add the studioHost property with your existing hostname, subsequent deployments should proceed without prompting you for it.