Failed to Switch from Node v20 to v22

[Jaskaran Deol]

Hello Support team, 

I had updated required Node version on bitbucket-pipelines.yml file for my node application. 

image : node:22.15.0

But post build & deployment for this node application,

When i validate the app for its node version it shows v20.12.2

this is concerning at the moment since app in question is a enterprise grade application.

Please review and revert for trouble shooting steps.

Note : I would like to point out, i had tried few troubleshooting steps, but none worked.

For example, setting 

`image : node:22` or other node v22 specific version, but post build and deployment app always always show node `v20.12.2`.

Last year, there were no issues, when i had updated the node version from v18 to v20 on bitbucket-pipelines.yml file.

Thank you.

[Theodora Boudale]

Hi @Jaskaran Deol and welcome to the community!

Please allow me to share some context first:

Assuming that your Pipelines builds run on Atlassian's infrastructure or with a self-hosted Linux Docker runner, these builds run in Docker containers. For every step of the build, a Docker container starts based on the image you have specified in your bitbucket-pipelines.yml file, the repo is cloned in this container, and then the commands from that step's script are executed. When the step finishes, the Docker container gets destroyed.

The option image : node:22.15.0 in your bitbucket-pipelines.yml file determines only the build environment, it tells Pipelines to start a Docker container based on the Docker Hub image node, tag 22.15.0, and run the build there. It doesn't have anything to do with the deployment environment.

As far as I know:

• If node is packaged into your app, you'll need to look into the build process, find out where you specify the version of node to be packaged and adjust it.
• Otherwise, the version of node used by an app is the one installed in the environment where the app is running.

Kind regards,
Theodora