[CVE-2024-33883] Bump ejs from 3.1.7 to 3.1.10

[ananzh]

Issue Resolved

#6769

Changelog

• security: [CVE-2024-33883] Bump ejs from 3.1.7 to 3.1.10

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.12%. Comparing base (8d50974) to head (02a3799).
Report is 13 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #6770       +/-   ##
===========================================
- Coverage   67.38%   55.12%   -12.27%     
===========================================
  Files        3443     1204     -2239     
  Lines       67795    24625    -43170     
  Branches    11032     4168     -6864     
===========================================
- Hits        45683    13574    -32109     
+ Misses      19440    10400     -9040     
+ Partials     2672      651     -2021     

Flag	Coverage Δ
Linux_1	?
Linux_2	55.12% <ø> (ø)
Linux_3	?
Linux_4	?
Windows_1	?
Windows_2	?
Windows_3	?
Windows_4	?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[virajsanghvi]

Approving as 3.1.101 doesn't seem to exist and lint errors seem unrelated...

[virajsanghvi]

I'm assuming the title should be update to 3.1.10 instead of 3.1.101?

[bandinib-amzn]

+1

[ananzh]

Yes. 1 should be `. Will correct it and thank you for the careful check.

[virajsanghvi]

Requesting change to accurate version

[virajsanghvi]

Should this be 3.1.10?

[ananzh]

Yes. 1 should be `. Will correct it and thank you for the careful check.

[bandinib-amzn]

+1

[ananzh]

@bandinib-amzn @virajsanghvi I corrected the typo. Could you two help me to re-check this fix?

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-6770-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 016dcfd82bb93ca3e64d4eaf54d9a34795c02891
# Push it to GitHub
git push --set-upstream origin backport/backport-6770-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-6770-to-2.x.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-6770-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 016dcfd82bb93ca3e64d4eaf54d9a34795c02891
# Push it to GitHub
git push --set-upstream origin backport/backport-6770-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-6770-to-2.x.

[BionIT]

Thanks @ananzh ! Found we have a manual backport #6924, thus removed the failed backport label