chore: upgrade node & mongo versions in ci, actions upgrades

[coopernetes]

• add newer Node versions to build in CI so we test against all major LTS versions
• do the same for mongodb versions; CI is building against an ancient, long EOL version (4.4, Mongo is on version 8.x).
• used ratchet to upgrade actions to their latest versions

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	0509d78
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/69401ae3b23fe2000908e8f8

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ❌ 1 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ✅ 0 package(s) with unknown licenses.

View full job summary

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.64%. Comparing base (e767463) to head (0509d78).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1315   +/-   ##
=======================================
  Coverage   80.64%   80.64%           
=======================================
  Files          65       65           
  Lines        4572     4572           
  Branches      776      776           
=======================================
  Hits         3687     3687           
  Misses        870      870           
  Partials       15       15           

☔ View full report in Codecov by Sentry.
📢 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.

[jescalada]

The CI was erroring out because CodeQL had a mismatched parameter internally (CODEQL_ACTION_VERSION: 4.31.7 despite the action version being 3.31.7).

I fixed it by bumping the action to 4.31.7 - this should cover us when v3 gets deprecated next year.

[jescalada]

@coopernetes LGTM, just wondering if the CodeQL action bump to v4 is appropriate here or if we have a reason to stay at v3. I think ratchet might've set it to 3.31.7 because it's the "Latest" on the codeql-action GH releases page.

[jescalada]

@coopernetes It seems we need to remove/update the check for "build (20.x, 4.4)" in order to merge the PR. Wonder if this can only be edited by repo admins, as I don't see it in the settings. 🤔

[coopernetes]

@coopernetes LGTM, just wondering if the CodeQL action bump to v4 is appropriate here or if we have a reason to stay at v3. I think ratchet might've set it to 3.31.7 because it's the "Latest" on the codeql-action GH releases page.

Fixed.

@coopernetes It seems we need to remove/update the check for "build (20.x, 4.4)" in order to merge the PR. Wonder if this can only be edited by repo admins, as I don't see it in the settings. 🤔

Yep - we'll need to tag the finos admin folks to update the check for us.

Let me experiment with a "wrapper" or "result" job that can report the result of all the matrix jobs in one shot. Then, when we upgrade language support in the future or change versions, we do not need to modify our CI check.

See https://github.com/orgs/community/discussions/26822

[coopernetes]

@finos-admin can we get a hand to update our branch protection required check rule? Please change it from: build (20.x, 4.4) to build result.

This new job runs a script which checks the results of the matrix jobs for each version combination. The result job isn't version specific and will remove the need to update the protection rule next time we add a new version to support in CI.

EDIT: Also sent a quick email to help@finos.org

[finos-admin]

@coopernetes the branch protection rule has been updated. The build (20.x, 4.4) check has been removed and replaced by build result.