Use Node.js 15.13.0 in CI

[olleolleolle]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

This fixes a warning in the CI Self-Check

❌ CI environment 'Node 15' uses an old Node.js minor version 15.12.0 instead of 15.13.0.
❌ CI does not have environments using the following versions of Node.js: 15.13.0.
Error: CI environments are not up-to-date with the latest Node.js versions.

Approach

Followed an old update to the CI and imitated it.

[codecov]

Codecov Report

Merging #7312 (879bdf0) into master (ba32dae) will decrease coverage by 0.03%.
The diff coverage is n/a.

❗ Current head 879bdf0 differs from pull request most recent head c0116b0. Consider uploading reports for the commit c0116b0 to get more accurate results

@@            Coverage Diff             @@
##           master    #7312      +/-   ##
==========================================
- Coverage   93.92%   93.89%   -0.04%     
==========================================
  Files         181      181              
  Lines       13190    13190              
==========================================
- Hits        12389    12385       -4     
- Misses        801      805       +4     

Impacted Files	Coverage Δ
src/Adapters/Auth/httpsRequest.js	95.23% <0.00%> (-4.77%)	⬇️
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	92.59% <0.00%> (-0.66%)	⬇️
src/RestWrite.js	93.84% <0.00%> (-0.17%)	⬇️
src/Adapters/Files/GridFSBucketAdapter.js	80.32% <0.00%> (+0.81%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ba32dae...c0116b0. Read the comment docs.

[mtrezza]

Thanks for the PR!

[mtrezza]

Can you please change the CI timeout from 15 to 20 to make the postgres check pass?

It's in the CI.yaml, check-postgres, timeout-minutes: 15

[olleolleolle]

Can you please change the CI timeout from 15 to 20 to make the postgres check pass?

It's in the CI.yaml, check-postgres, timeout-minutes: 15

I made a commit, from my phone, did it come out right?

[mtrezza]

Yes, but could you try with 30mins? Not sure if it's just the test needing more time or a faulty test.

[dplewis]

@mtrezza As I mentioned the flaky timeout tests (batch requests tests) will always be there until fixed via #7283

Feel free to ignore it until then as an increase in timeout to 30 minutes won't help and waist Github Action credits (I don't know if we have unlimited credits being open sourced).

[mtrezza]

@dplewis Does this only affect one Postgres test, or all Postgres tests?

[dplewis]

Its flaky so random but 14/15 passing test suites is passing to me

[mtrezza]

Okay, so we'll set the timeout back to 15 and just re-run until it passes, I guess, thanks for clearing this up.

@olleolleolle Apologies for the confusion, would you please set this back to 15 and we'll just re-run. done

[parseplatformorg]

🎉 This change has been released in version 5.0.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 5.0.0