noticing some curious behavior on prisma cloud. wh...
# orm-help
c
noticing some curious behavior on prisma cloud. when creating a new service from scratch, it appears to default to prisma 1.23 (with no clear path to choose a version or upgrade). is this the latest supported version of prisma on prisma cloud?
the dev server seems to be beta but ideally i'd like to work against 1.31 final
j
if you click the little gear icon, theres an upgrade cluster button
@Jared i don’t see an upgrade cluster button for heroku-hosted servers
i’ve been following the steps outlined by wwwillchen at the above link to manually upgrade
p
I'm wondering about the same thing, were you able to find out any more information?
c
Yep I’m on Heroku as well so maybe that’s the discrepancy. Is it better to define the prisma server manually?
j
@patrickdevivo @cedric see above link! the docs are geared towards either a local docker setup or the demo servers. the prisma folks control the version that runs on the prisma-cloud instantiated heroku servers…and it’s not kept in sync with the demo servers. you can either downgrade your globally installed prisma package to 1.23 or you can manually upgrade the heroko image as wwwillchen explains in the above linked thread.
c
Yep, we wrote our app to use the new data model so we’ll upgrade
j
to clarify, the prisma folks control the initial prisma version that’s deployed to heroku. you’re free to update it if necessary.
p
👍 thanks for the info
s
@Jonathan Once again super helpful. Thanks 👍