Security update sfcc node version

[joyet-simon]

Reason for change

Linear task

Code changes

How to test

As a reviewer, you are encouraged to test the PR locally.

Checklist for authors and reviewers

• The title of the PR uses business wording, not technical jargon, for the changelog readers to understand it
• The PR implements the changes asked in the referenced task / issue
• The automated tests are compliant with the testing strategy
• The tests are relevant, and cover the corner/error cases, not only the happy path
• You understand the impact of this PR on existing code/features
• The changes include adequate logging and Datadog traces
• Documentation is updated (API, developer documentation, ADR, Notion...)

Non applicable

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[FranceBe]

Hi @gdraynz ,
We changed node version, but I don't get where this CI check is coming from ?
I don't see any other reference to node 12 in the repo, what am I missing ? :(

[gdraynz]

The required check is in the branch protection rules, I will do the swap.

[gdraynz]

@FranceBe Done, sorry I thought I did earlier 😁