@prisma/language-server
versions overlap for versions that are for Insider vs. stable version
#868
Labels
bug/2-confirmed
Bug has been reproduced and confirmed.
domain/schema
Issue in the "Schema" domain: Prisma Schema, Introspection, Migrations etc.
kind/bug
A reported bug.
topic: automation
topic: ci
topic: internal
During the release process of the VSCode extension for Prisma CLI
3.0.1
workflow 3 unexpectedly crashed. Turned out there is an overlap in the versioning scheme now we start with lower minor versions again:3.0.1
(for Prisma CLI3.0.1
) =>@prisma/language-server@3.0.1
3.0.1
(for Prisma CLI2.3.1-dev.1
) =>@prisma/language-server@3.0.1
(from a looong time ago)This leads to a crash in "3. Unit tests for LSP and publish" as the
npm publish
does not work.(The overlapping version numbers "make sense" as the
@prisma/language-server
version is tightly coupled with the version string of the VSCode extension. We did not anticipate any problem back when we make the decision to just take both versions, both the one of the Insiders and the stable extension, and apply it to the Npm package. That was a mistake in hindsight)Workaround
packages/language-server/package.json
(andpackage-lock.json
) (e.g. +100 on the patch to make it3.0.101
)3.0.101
3.0.1
) to finish the build and publish.The text was updated successfully, but these errors were encountered: