Upgrading node on code catalyst...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! !! !! Node 16 has reached end-of-life on 2023-09-11 and is not supported. !! !! Please upgrade to a supported node version as soon as possible. !! !! !! !! This software is currently running on node v16.20.1. !! !! As of the current release of this software, supported node releases are: !! !! - ^20.0.0 (Planned end-of-life: 2026-04-30) !! !! - ^18.0.0 (Planned end-of-life: 2025-04-30) !! !! !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

This is'nt for my actions.. I want to upgrade node in the dev environment

I havent done it, but maybe this guide helps? https://repost.aws/articles/ARBTATztMgQOeYyMZ9IAmxDw/configuring-codecatalyst-dev-environments

It shows you how to customize your dev environment using the devfile.yaml and if I read it correctly it should allow you to update node aswell!

And of course - your package.json also needs to then use the newer node version...?

I coud'tn figure out a way @Lockhead

I'll point the team to this to see if they can provide any further updates.

Hi there, Amazon CodeCatalyst now supports Node 18 and Node 20 with Devfile images 3.0. You can find more details at [here]. Please feel free to reach out if you encounter any issues while upgrading the devfile image

The Devfile is used for Dev Environment in CodeCatalyst. What we need is Workflows Compute (EC2 fleet) for build Actions which support Node 18 | 20. CodeCatalyst only provides the Amazon Linux 2 Operating system on-demand fleets at the moment and this OS uses Node 16, not able to upgrade

Now using node v18.19.0
/tmp/codecatalyst/binaries/nvm/versions/node/v18.19.0/bin/node
node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)

Hello, there are a few options at the moment for running a build action using a later version of node. We are working to provide additional options around this as node.js 16 approaches its end of life date. We will share more information about that when we can.

For now, you could

1. Download the version of node you want to use in the first step of your action (this will take time)
2. Use your own build image
3. Use the ARM image if it fits for your use case. This uses node18.

There’s more information about this topic here.