-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Studio should pin prisma dependencies to avoid problems during prisma
patch releases.
#766
Comments
Ran into this today while doing a patch release of @prisma/studio-server 0.422.0
├─┬ @prisma/sdk 2.31.0-dev.19
│ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ ├─┬ @types/debug 4.1.7
│ │ │ └── @types/ms 0.7.31
│ │ ├─┬ debug 4.3.2
│ │ │ └── ms 2.1.2
│ │ └── ms 2.1.3
│ ├─┬ @prisma/engine-core 2.31.0-dev.19
│ │ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ │ ├─┬ @types/debug 4.1.7
│ │ │ │ └── @types/ms 0.7.31
│ │ │ ├─┬ debug 4.3.2
│ │ │ │ └── ms 2.1.2
│ │ │ └── ms 2.1.3
│ │ ├── @prisma/engines 2.31.0-11.c6aa2685dff09984e6656f5d99a90b9e90eabbce
│ │ ├─┬ @prisma/generator-helper 2.31.0-dev.19
│ │ │ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ │ │ ├─┬ @types/debug 4.1.7
│ │ │ │ │ └── @types/ms 0.7.31
│ │ │ │ ├─┬ debug 4.3.2
...
│ ├─┬ @prisma/generator-helper 2.31.0-dev.19
│ │ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ │ ├─┬ @types/debug 4.1.7
│ │ │ │ └── @types/ms 0.7.31
│ │ │ ├─┬ debug 4.3.2
│ │ │ │ └── ms 2.1.2
│ │ │ └── ms 2.1.3
│ │ ├─┬ @types/cross-spawn 6.0.2
│ │ │ └── @types/node 14.17.6
│ │ ├─┬ chalk 4.1.2
...
├─┬ @prisma/studio-pcw 0.422.0
│ ├─┬ @prisma/sdk 2.31.0-dev.19 peer
│ │ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ │ ├─┬ @types/debug 4.1.7
│ │ │ │ └── @types/ms 0.7.31
│ │ │ ├─┬ debug 4.3.2
│ │ │ │ └── ms 2.1.2
│ │ │ └── ms 2.1.3
│ │ ├─┬ @prisma/engine-core 2.31.0-dev.19
│ │ │ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ │ │ ├─┬ @types/debug 4.1.7
│ │ │ │ │ └── @types/ms 0.7.31
│ │ │ │ ├─┬ debug 4.3.2
│ │ │ │ │ └── ms 2.1.2
│ │ │ │ └── ms 2.1.3
│ │ │ ├── @prisma/engines 2.31.0-11.c6aa2685dff09984e6656f5d99a90b9e90eabbce
│ │ │ ├─┬ @prisma/generator-helper 2.31.0-dev.19
│ │ │ │ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ │ │ │ ├─┬ @types/debug 4.1.7
│ │ │ │ │ │ └── @types/ms 0.7.31
...
│ │ ├─┬ @prisma/generator-helper 2.31.0-dev.19
│ │ │ ├─┬ @prisma/debug 2.31.0-dev.19
│ │ │ │ ├─┬ @types/debug 4.1.7
│ │ │ │ │ └── @types/ms 0.7.31
│ │ │ │ ├─┬ debug 4.3.2
│ │ │ │ │ └── ms 2.1.2
│ │ │ │ └── ms 2.1.3
... |
Check with @madebysid on Monday about the reasons for unpinning the deps, before proceeding with any changes. |
This is done now! |
Sid
I tried an esbuild plugin but it failed |
So this is not done for this release, Prisma CLI with this latest Studio breaks and was reverted, we can look at it later Thread at https://prisma-company.slack.com/archives/CC8F34ALF/p1630350532018100 |
I guess we can close this now? |
I think we can close indeed! https://github.com/prisma/studio-code/blob/main/packages/pcw/package.json#L44-L45 |
During the
prisma/prisma
2.29.1
patch release we randomly found out that we needed to override Studio's dependency because they are not pinned.prisma/prisma@88a9abe
We could totally have miss that if there was no breaking change introduced on a more recent dev version when we did the release.
It seems that Studio was pinning the versions before and stopped after
2.27.0
https://github.com/prisma/studio-code/commit/1b5dd7a8073401fbf55086a5c66b43fd4bc89233#diff-34be044c758fdb7c9dced6a2c56893d0ead78ae7b40869576f02d120e9ff0456
Is there a specific reason that needed us to unpin?
Happy to send a PR.
The text was updated successfully, but these errors were encountered: