Whenever we ship Next.js releases, we have been running them in production across our portfolio of websites for weeks. For vercel.com we upgrade to latest canary via an automated PR. Does stuff sometimes break? Yes Is that better for all Next.js users? Yes Does it motivate us to invest into additional automated tests: Yes! Visual transition regressions like this are particularly hard to catch using automated tests. Still better to catch them on https://t.co/jDmpqA2KqX than letting them slip into a stable release!
oof this is fixed now - we're always dogfooding the latest next canary version which allows us to find bugs / edge cases like the one that caused this still we need more e2e tests here so it doesn't affect customers - i'll be improving our test coverage here