My Deployment still detects an old version of v16.19.0 even though I have updated to v18.17.0

[Fobeworks]

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v18.17.0

Amplify CLI Version

12.10.0

What operating system are you using?

ubuntu

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

I edited the amplify.yml file to contain the v18.17.0 of node which was what the error was indicating

Describe the bug

During my deployment on amplify initially, I got the error that my version of node installed is not compatible, I upgraded using nvm and edited my package.json file, even my package-lock.json file shows the latest version yet when I deploy the error still shows me that am using v16.19.0. When I run node -v I get v18.19.0 which is what I have upgraded to but yet my build fails. I have even modified the amplify.yml file to reflect the node version as stated but I still get the error. How can I SOLVE this ASAP.

Expected behavior

I expect my application to get to deployment and render my website using aws amplify.

Reproduction steps

Starting phase: preBuild

                             # Executing command: npm ci

2023-12-18T19:13:08.001Z [WARNING]: npm
2023-12-18T19:13:08.003Z [WARNING]: WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18.17.0', npm: '>=8.0.0' },
npm WARN EBADENGINE current: { node: 'v16.19.0', npm: '8.19.3' }
npm WARN EBADENGINE }
2023-12-18T19:13:08.005Z [WARNING]: npm WARN
2023-12-18T19:13:08.005Z [WARNING]: EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18.17.0' },
npm WARN EBADENGINE current: { node: 'v16.19.0', npm: '8.19.3' }
npm WARN EBADENGINE }
2023-12-18T19:13:19.480Z [INFO]: added 452 packages, and audited 453 packages in 14s
2023-12-18T19:13:19.483Z [INFO]: 108 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
2023-12-18T19:13:19.503Z [INFO]: # Completed phase: preBuild
# Starting phase: build
# Executing command: npm run build
2023-12-18T19:13:19.803Z [INFO]: > [email protected] build
> next build
2023-12-18T19:13:19.853Z [WARNING]: You are using Node.js 16.19.0. For Next.js, Node.js version >= v18.17.0 is required.
2023-12-18T19:13:19.861Z [ERROR]: !!! Build failed
2023-12-18T19:13:19.861Z [INFO]: Please read more about Amplify Hosting's support for SSR frameworks to find if your build failure is related to an unsupported feature: https://docs.aws.amazon.com/amplify/latest/userguide/amplify-ssr-framework-support.html. You may also find this troubleshooting guide useful: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html
2023-12-18T19:13:19.861Z [ERROR]: !!! Non-Zero Exit Code detected
2023-12-18T19:13:19.861Z [INFO]: # Starting environment caching...
2023-12-18T19:13:19.862Z [INFO]: # Environment caching completed
Terminating logging...

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[calavera]

Try changing the base image that you use to deploy your Next.js 14 application. See this comment on how to do it: #3773 (comment)

[ethyaan]

@calavera Thank you that saved my time.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[github-actions]

This issue has been automatically locked.