remotion-dev/remotion · error · Error

The tag for Remotion version ${VERSION} was not found in the

Error message

The tag for Remotion version ${VERSION} was not found in the Cloud run registry.

What it means

Thrown by validateImageRemotionVersion() after querying the Artifact Registry (projects/remotion-dev/.../repositories/production/packages/render) for tags and finding none equal to the installed package VERSION. The check ensures the Docker image tag for your @remotion/cloudrun version exists before attempting to deploy a service from it. A missing tag usually means a prerelease, yanked, or not-yet-published version.

Source

Thrown at packages/cloudrun/src/shared/validate-image-remotion-version.ts:24

		projectId: process.env.REMOTION_GCP_PROJECT_ID,
		credentials: {
			client_email: process.env.REMOTION_GCP_CLIENT_EMAIL,
			private_key: process.env.REMOTION_GCP_PRIVATE_KEY,
		},
	});
	const listedTags = await client.listTags({
		parent:
			'projects/remotion-dev/locations/us/repositories/production/packages/render',
	});

	for (const tag of listedTags[0]) {
		if (VERSION === tag.name?.split('/').pop()) {
			// if match is found, exit the function
			return;
		}
	}

	throw new Error(
		`The tag for Remotion version ${VERSION} was not found in the Cloud run registry.`,
	);
};

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Install a published release: `npm i @remotion/cloudrun@latest` then redeploy.
2. Wait for the image tag to be published if you are tracking a freshly released version.
3. If you are a Remotion contributor testing a local version, build and push the image yourself or use a pinned released version.

Example fix

// before: local bump to 5.0.0-canary not in registry
// $ npm i @remotion/cloudrun@5.0.0-canary.abcdef
// $ npx remotion cloudrun services deploy
// after: use a published release
// $ npm i @remotion/cloudrun@latest
// $ npx remotion cloudrun services deploy

import pkg from '@remotion/cloudrun/package.json';
// Only attempt deploy on a published (non-prerelease) version
if (pkg.version.includes('-')) {
  throw new Error(`${pkg.version} looks like a prerelease; its image tag may not be in the registry. Use a published release.`);
}

function isLikelyPublishedRelease(version: string): boolean {
  return /^\d+\.\d+\.\d+$/.test(version);
}

try {
  await deployService(opts);
} catch (err) {
  if (err instanceof Error && err.message.includes('was not found in the Cloud run registry')) {
    throw new Error('Image tag missing. Install a published @remotion/cloudrun release and redeploy.');
  }
  throw err;
}

When it happens

Trigger: Calling deployService() (or any flow that calls validateImageRemotionVersion) with an @remotion/cloudrun version whose image tag was never published to the registry — e.g., a local build, a canary, or a version newer than the latest published image.

Common situations: Running a local/linked build of @remotion/cloudrun with a bumped version not yet released; using a prerelease tag; the registry was not yet updated when you upgraded.

Related errors

• serveURL ERROR. File "${fileName}" not found in bucket "${bu
• ARTIFACT_REGISTRY_ENV is ${process.env.ARTIFACT_REGISTRY_ENV
• Version mismatch: When calling renderMediaOnCloudRun(), you
• Should not download a browser in Cloud Run
• Version ${reactDomVersion} of "react-dom" is not supported b

AI-assisted analysis of remotion-dev/remotion@78fe4bb3fd (2026-08-12). Data as JSON: /api/errors/eb3a5d58afaf6b98. Report an issue: GitHub.