Thoughts on formalizing compatibility tests to provide list of supported version configurations?

[kevin-mitchell]

I am currently in the position where I'm wondering, "what version of Next.js is compatible with which version of open-next is compatible with which version of cdk-nextjs?"

It would be really handy to be able to find this out either by looking at documentation somewhere, or by running a reliable automated test, or at least by running a manual process to validate all functionality is working.

open-next / SST has a set of automated tests that appear to run (maybe automatically?) to check compatability between Next.js versions and open-next (I assume?), perhaps something from here could be incorporated into this project somehow?

https://github.com/sst/open-next/actions/runs/6400188581/job/17373444061

Does this seem like something that could get done? Would it actually be useful?

[khuezy]

The open-next discord channel has an E2E test bot that reports the nextjs version and if the test passes/fails. It runs at 0:00UTC (or 6PM PDT)

[khuezy]

You could add another flow to update a GH Pages w/ a table or compatible versions.

[kevin-mitchell]

This is for open-next + SST though, correct?

This is the setup for github actions: https://github.com/sst/open-next/blob/main/.github/workflows/e2e.yml

The readme explains the tests: https://github.com/sst/open-next/tree/main/packages/tests-e2e

And this is the app that is actually deployed for the test: https://github.com/sst/open-next/tree/main/example

Would it make sense to have something similar (perhaps literally exactly the same thing, just deploying to with this project instead of SST)?

[khuezy]

Yeah, you'll need @revmischa to set up the AWS creds for this GH for the deployment

[bestickley]

I think this is a great idea. My time for this project is focused on feature development, but please take a stab at this @kevin-mitchell. It would be really helpful.

[kevin-mitchell]

Cool I'll probably take a look this week.