MongoDB 4, 5 CI jobs fail for LTS branch release-7.x.x

[mtrezza]

New Issue Checklist

• Report security issues confidentially.
• Any contribution is under this license.
• Before posting search existing issues.

Issue Description

MongoDB 4, 5 CI jobs fail because the mongo-runner doesn't seem to find the MongoDB 4 and 5 images. Likely because they reached their EOL. Parse Server 7 is in LTS and merging any PR would be risky without CI for older MongoDB versions which keep being supported by Parse Server 7 until end of 2025.

Steps to reproduce

See https://github.com/parse-community/parse-server/actions/runs/12729036099/job/35480354207?pr=9525

Proposed Solution

Try to download different MongoDB versions of the required major version, if they are available, for example the latest release of 4.x.x and 5.x.x.

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[dblythy]

Strangely I have no problem running mongodb-runner start -t replset --version 4.2.25 -- --port 27017 locally, but it seems to fail in the CI

[mtrezza]

Could it be that you are running it on a different arch?

[dblythy]

Maybe, tested on macOS with node v22.12.0

[mtrezza]

I don't think that GitHub Actions runs on arm64 (if you have a Mx chip), more likely on x86_64 by default. But it may be a completely different issue. We could try to lower the Node version; it currently runs with Node 22.12.0, maybe try Node 18. Or you could try to use Node 22.10.0 on your local machine and see whether the issue occurs.

[parseplatformorg]

🎉 This change has been released in version 7.5.0