[francoisferrand]

Following the eMudhra/emSign CA compromise, this moves the image to Node 24.22.1. That release ships the NSS 3.131.1 root store, which blocks the compromised intermediates.

The utapi Python scripts get the same fix: certifi goes to 2026.10.19 (GHSA-6q48-6c7w-9gw2). The venv also upgrades pip to >= 26.2.2, because pip vendors its own certifi.

yarn.lock is refreshed to pick up the patched follow-redirects, ip-address and body-parser, all within their existing ranges and without adding duplicates. The other yarn audit findings come from upstream pins (markdownlint in the lint config, @azure/msal-node through arsenal) or have no fix yet.

The last commit bumps the version to 1.20.1 for the release.

Issue: S3UTILS-255

[bert-e]

Hello francoisferrand,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/bypass_source_branch_lineage	Bypass the cross-branch contamination check	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request.
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[claude]

🔄 Claude Code Review: reviewing...

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.00%. Comparing base (67b740e) to head (c5312ba).
⚠️ Report is 4 commits behind head on development/1.20.

Additional details and impacted files

@@                Coverage Diff                @@
##           development/1.20     #417   +/-   ##
=================================================
  Coverage             49.00%   49.00%           
=================================================
  Files                    89       89           
  Lines                  6503     6503           
  Branches               1411     1411           
=================================================
  Hits                   3187     3187           
  Misses                 3262     3262           
  Partials                 54       54           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[francoisferrand]

/approve

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge improvement/S3UTILS-255-bump-node-24.22.1 into
  development/1.20
• w/1/improvement/S3UTILS-255-bump-node-24.22.1 will be merged into development/1

The following branches will NOT be impacted:

• development/1.13
• development/1.14
• development/1.15
• development/1.16
• development/1.17
• development/1.18
• development/1.19
• development/1.4
• development/1.7

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/1.20

• ✔️ development/1

The following branches have NOT changed:

• development/1.13
• development/1.14
• development/1.15
• development/1.16
• development/1.17
• development/1.18
• development/1.19
• development/1.4
• development/1.7

This pull request did not target the following hotfix branch(es) so they
were left untouched:

• hotfix/1.14.19
• hotfix/1.14.0

Please check the status of the associated issue S3UTILS-255.

Goodbye francoisferrand.

The following options are set: approve