build(deps): updating JDK/node/actions/JS deps/native deps

[mikehardy]

Description

Periodic maintenance

• node 20 -> 22
• JDK 17 -> 21
• codecov-action 4 -> 5
• react-native 0.77 -> 0.78
• yarn 4.6.0 -> 4.9.1 (supports provenance now, should be visible as little green check mark on packages like here after publish: https://www.npmjs.com/package/@react-native-firebase/app?activeTab=versions similar to https://www.npmjs.com/package/@notifee/react-native?activeTab=versions)

Related issues

none logged - it's our local infrastructure

Release Summary

semantic release commits, none of which should trigger a release

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
  • Other (macOS, web)
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

CI will exercise everything, but also local test runs

• ⚠️ Codecov needs verification that uploads are still working, I have looked at the detailed CI run logs and we are still getting coverage tracking, so the v4 -> v5 upgrade seems okay but something is wrong with the upload files ios / android ?, e.g.: https://app.codecov.io/github/invertase/react-native-firebase/commit/08d58f67c73c715e134a2b29e5c91194a09626c3

• ccache behavior needs verification after moving env vars, I have looked at the detailed CI run logs and I see cache misses but that's expected at the moment - it is caching things though, which is good

  • https://github.com/invertase/react-native-firebase/actions/runs/14576785259/job/40884537477?pr=8482#step:40:11

• Vercel settings were updated to build with node22 at the same time, the preview will show whether it worked or not (check reference API for typedoc generation as well) https://react-native-firebase-6mtkf83zt-invertase.vercel.app/

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-firebase	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 25, 2025 0:20am

[mikehardy]

Digging into coverage issue, at least for android, it appears the native coverage and the javascript coverage were both empty for some reason, from the downloaded coverage report on codecov https://app.codecov.io/github/invertase/react-native-firebase/commit/08d58f67c73c715e134a2b29e5c91194a09626c3

<<<<<< network

# path=/home/runner/work/react-native-firebase/react-native-firebase/tests/android/app/build/reports/jacoco/jacocoAndroidTestReport/jacocoAndroidTestReport.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><!DOCTYPE report PUBLIC "-//JACOCO//DTD Report 1.1//EN" "report.dtd"><report name="app"/>
<<<<<< EOF

# path=/home/runner/work/react-native-firebase/react-native-firebase/coverage/lcov.info

<<<<<< EOF

This seems to happen on quite a lot of our pull requests though, yet we still have good coverage on main most of the time.
Not sure exactly what's going on here but it seems flaky vs permanently busted

[MichaelVerdon]

LGTM, surely we can make a script to make this task less laborious like I made on FlutterFire? What do you think?

[mikehardy]

@MichaelVerdon I'm still working through it - re: script, hard to say. I mean, I love a script (witness make-demo.sh and I've got piles of others). But before this is done, it's going to involve upgrades of deps in these ecosystems:

• github actions (dependabot helps, but we still have to do it)
• javascript deps (and there are breaking changes all over, the non-breaking ones are scriptable but also take effectively no time)
• react-native (need to forward port things every time)
• native java items (check + forward port things)
• the node and jdk and github runner versions used in CI (trivial to do, the time taken is all checking logs to make sure things work)

So things could be automated a bit but there would be an automation cost and maintenance cost for it, while I think the real cost of the activity is in verification and forward-porting