Test all officially supported versions of Prisma in CI

[jasonkuhrt]

What

• We list multiple versions of Prisma in our peer dependency requirements
• In CI we only test what is in our dev dependencies
• This means we are not testing everything we claim to support

Why

• Increase confidence both us and our users

How

• gh matrix, prisma version dimension matching what we put into our peer dep package json value
• install a version of prisma right before testing

Notes

• This is going to get intense to test each combo of prisma/Node/OS... 😱

[jasonkuhrt]

CC @janpio fyi thought you might find this one interesting

[janpio]

Indeed 👍

I think you can limit Prisma version testing to one Node version, and potentially also OS as you are testing the current Prisma version on all of those and Prisma itself is being tested on all relevant Node versions and OS.

[jasonkuhrt]

Does this sound good to you?

• latest officially supported prisma on all node/OS combos
• all trailing officially supported prisma versions on JUST latest LTS Node & ubuntu

[jasonkuhrt]

Also: we should note in the docs that officially supporting a version of Prisma means only its latest patch version under that minor series. So yes 2.24.1 and NO 2.24.0, etc.

This detail reflects the testing strategy and thus keeps things more honest/accurate.

The implication is that if there is a bug with the combo of Nexus Prisma and 2.24.0 but NOT 2.24.1 then we wouldn't be obliged to do anything in Nexus Prisma.

[janpio]

Yep, that all makes a lot of sense.

[rostislav-simonik-nexus-prisma-admin]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

• npm package (@next-major dist-tag)
• GitHub release

Your semantic-release bot 📦🚀