Prisma errors when not using the major.minor.patch versioning system

Bug description

I recently changed my versioning system to use architecture.major.minor.patch instead of the usual major.minor.patch. When I did this and run npx prisma introspect, it errors with “Invalid version”

It does not make any sense that prisma would complain about this.

How to reproduce

1. Go to package.json
2. Change “version” to “0.1.0.0”
3. Run npx prisma introspect
4. See error “Invalid version”

Expected behavior

Prisma should be able to accept a versioning system that is not the usual major.minor.patch, so long as it is a string.

Prisma information

Not required

Environment & setup

• OS: Windows 10
• Database: MySQL
• Node.js version: 16.1.0

Prisma Version

prisma               : 2.23.0
@prisma/client       : 2.22.1
Current platform     : windows
Query Engine         : query-engine adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules\@prisma\engines\query-engine-windows.exe)
Migration Engine     : migration-engine-cli adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules\@prisma\engines\migration-engine-windows.exe)
Introspection Engine : introspection-core adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules\@prisma\engines\introspection-engine-windows.exe)
Format Binary        : prisma-fmt adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules\@prisma\engines\prisma-fmt-windows.exe)
Default Engines Hash : adf5e8cba3daf12d456d911d72b6e9418681b28b
Studio               : 0.393.0

[pantharshit00]

code/reproductions/issue_7317 is 📦 v0.1.0.0 via  v14.17.0
❯ DEBUG=* prisma introspect
  prisma:loadEnv project root found at C:\Users\harshit\code\reproductions\issue_7317\package.json +0ms
  prisma:tryLoadEnv Environment variables not found at null +0ms
  prisma:tryLoadEnv Environment variables loaded from ./prisma/.env +1ms
Environment variables loaded from prisma\.env
  prisma:engines using NAPI: false +0ms
  prisma:engines binaries to download query-engine, migration-engine, introspection-engine, prisma-fmt +0ms
Error: Error: Invalid version: "0.1.0.0"
    at Object.fixVersionField (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:9584:15)
    at C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:9900:40
    at Array.forEach (<anonymous>)
    at normalize (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:9899:17)
    at module2.exports (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:9926:26)
    at async Object.module2.exports [as default] (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:9957:20)
    at async getSchemaPathFromPackageJson (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:10017:21)
    at async getSchemaPathInternal (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:10008:36)
    at async DbPull2.parse (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:63731:24)
    at async main (C:\Users\harshit\AppData\Roaming\npm\node_modules\prisma\build\index.js:109791:18)

[ghost]

This is definitely unexpected @HurricaneDancer - a side effect of a library we are using. We will try to get rid of that. Sorry.

Thanks!