Closed matthewmueller closed 4 years ago
Update: I didn't realize that CI was auto-publishing based on prisma2's version, not vscode's.
This makes our job easier. Rather than manually updating the SHA, we just need to add another few lines to CI to additionally pull prisma.version
from prisma2 and write it to prisma.version
in vscode.
Currently, every automated release will maintain an old version of prisma-fmt until we manually update that SHA and manually publish.
Right now we need to manually increment the SHA in the package.json's
prisma.version
.We should use a github action to occasionally check for a new SHA, update it and commit it if that's the case.