✅ - CI/CD doesn’t deploy changes after upgrading Next.js to v13 | AWS Amplify | Page 1

hushed scarab Feb 6, 2023, 4:01 PM

#

HI!

We currently use AWS Amplify and have an issue with this.

The issue appeared after we tried to update Next.js to the last 13v and use it with Amplify.

Currently, after every new commit merges the build process is successful and each env is deployed, but for some reason, we don’t see new changes on the website and seems like it is cashed in the state of the last successful build before upgrading Next.js.

We tried to fix that on Rewrites and redirects page. But not sure if everything is configured well there.

On the other hand, new environments working fine with the last changes in case of clearing all configuration in the Rewrites and redirects page, otherwise - no.
Our goal is to fix this issue and make sure that the new features will be visible again in our main environment.

Thanks!

silver sundial Feb 6, 2023, 4:07 PM

#

Have you deleted the cloudfront rule under rewrite/redirect section after upgrading ?

hushed scarab Feb 6, 2023, 4:10 PM

#

silver sundial Have you deleted the cloudfront rule under rewrite/redirect section after upgrad...

Nope. First we faced the issue, and than started experimenting and looking for the problem

silver sundial Feb 6, 2023, 4:11 PM

#

That rule is not required after the app is migrated to WEB_COMPUTE. Try removing that rule and redeploy.

hushed scarab Feb 6, 2023, 4:43 PM

#

silver sundial That rule is not required after the app is migrated to WEB_COMPUTE. Try removing...

Thanks!
Seems working

silver sundial Feb 6, 2023, 4:46 PM

#

Cool

silver lanceBOT Feb 6, 2023, 5:45 PM

#

✅ - CI/CD doesn’t deploy changes after upgrading Next.js to v13

#✅ - CI/CD doesn’t deploy changes after upgrading Next.js to v13