Try removing the .vercel directory in your project folder and then run vercel again to re-initialize the project. The .vercel directory contains local configuration files for your Vercel project.
Removing this directory clears out any potentially outdated or corrupted local configuration.
Running vercel again after removing the directory will re-initialize the project, creating a fresh configuration.
The name change may be why you can’t redeploy an older build. And if the project is called [project name] now, that explains why vercel link doesn’t work with [project name].ai as the name. No project with the old name currently exists.
If you link to the new project name and create a new deployment, are you able to redeploy that one?
I understand, @josefnorlin. I wouldn’t expect it to be able to relink with the old name unless you changed the project name back to the old name. The vercel link command will only work with an existing project name. If the local repo is currently linked with the new project name, that’s good news!
You should still be able to redeploy using the vercel redeploy [deployment-id or url] command. Note that this requires either the unique deployment url or the deployment id. It will fail if an existing deployment is not specified.
You should also be able to create new deployments using the vercel deploy or vercel deploy --prod command.
I’m happy to look into it further if you still run into trouble with either of those commands. I’ll need to know the project name, the error message, CLI version, and the exact steps you followed leading to the error.