[Enhancement] Update Prisma from 4.13.0 to 5.8.1

[petradonka]

WHY are these changes introduced?

Fixes #400

Upgrade the Prisma ORM version of @shopify/shopify-app-session-storage-prisma to the latest to incorporate the improvements in the latest versions.

WHAT is this pull request doing?

Simple dependency bump. No breaking changes are known to be relevant to @shopify/shopify-app-session-storage-prisma.

Type of change

• Patch: Bug (non-breaking change which fixes an issue)
• Minor: New feature (non-breaking change which adds functionality)
• Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have used yarn changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)
• I have added/updated tests for this change
• I have documented new APIs/updated the documentation for modified APIs (for public APIs)

[petradonka]

I believe there will also be other version bumps needed in other repos, because of the peer dependency version requirement:

• https://github.com/Shopify/shopify-app-template-remix/blob/main/package.json#L22-L38
• https://github.com/Shopify/example-app--qr-code--remix/blob/main/package.json#L20-L38
• https://github.com/Shopify/example-app--payments-app-template--remix/blob/main-js/package.json#L22-L38

What's the best way to go about this to make sure any dependent changes across repos are in sync?

[petradonka]

I have signed the CLA!

[paulomarg]

Hey Petra, thanks for contributing! I'll be reviewing this today, but I expect it'll be an easy one if there are no breaking changes :)

[paulomarg]

Tested it on the template and it works just fine :)

[paulomarg]

I wonder if this should be a major bump instead - because the template also imports prisma directly, there'll be a version mismatch for existing apps that will block them from updating this package until they go over to prisma 5, and that might mean some breaking changes to their app.

[petradonka]

That'd make sense for me. Should I update the changeset?

I think this also relates to my question above: how do we best go about "syncing" this bump across the various repos, exactly because of that peer dep version mismatch?

[paulomarg]

Oh sorry, I totally missed that comment. And yeah, we'll need to bump the dependency on all of those repos - the major version bump would prevent them from breaking in the meantime, which is nice.

Once we merge / release this, we'll need to bump each of the template repos, but that should be pretty easy.

I'd say let's go with a major bump and once we release it I can create separate PRs for those, it should be a quick update.

[petradonka]

Perfect! I changed this to a major bump, changeset should be good to go then.

[blanklob]

This is not published to npm right? @paulomarg

[paulomarg]

Not yet, we're planning on publishing soon!