Potential pipeline 🔥 of language-tools with versioning change of @prisma/engines

[Jolg42]

Related to the PR prisma/prisma#13769

We found that the language-tools pipeline relies on the @prisma/engines version to resolve the same version from @prisma/prisma-fmt-wasm
Which currently looks like 3.16.0-43.81a0ee489e5f8c8ce98440028ea9050092430503 (engine hash format)

language-tools/scripts/update_package_json_files.js

Lines 80 to 90 in a4c7d9c

	// engines hash
	const engineVersion = prismaCLIDeps['@prisma/engines'] // 2.26.0-23.9b816b3aa13cc270074f172f30d6eda8a8ce867d
	const sha = engineVersion.split('.')[3]
	let languageServerPackageJson = getPackageJsonContent({
	path: languageServerPackageJsonPath,
	})
	languageServerPackageJson['prisma']['enginesVersion'] = sha
	// engines version
	languageServerPackageJson['dependencies']['@prisma/prisma-fmt-wasm'] =
	engineVersion

@prisma/engines version should change to the prisma monorepo version like 3.16.0-dev.93 (dev) or 3.16.0 (stable) which is missing the engine hash.

We could maybe solve this by adding the @prisma/engines-version dependency to the prisma CLI package.json

[millsp]

We can use import { enginesVersion } from '@prisma/engines', which gives the sha.

[Jolg42]

Yes! Let's try that later