build(deps): update all dependencies to most-current possible

[mikehardy]

Description

This just brings our internal infrastructure and test app etc up to date.

REVIEWERS

Reviewers: look at this one commit by commit. Each commit is separate and does one thing. Review should be really easy that way

Step 1 ✅: update all dependencies to their highest version that is not a semver-major change

This gets the easy stuff out of the way and gives us a stable baseline for the harder semver-major work

Step 2 ✅: handle non-react-native semver-majors - this is to try to get a working baseline of any big changes before we bump react-native and it's related packages

• node minimum requirements changed to v20 in some packages, updated github workflows etc
• inquirer changed, forward-ported to new API
• detox and firebase rules-unit-testing changed and our patches no longer applied, forward-ported patches
• sinonjs changed but just needed a transitive dep addition of assert
• coverage reporting on codecov seems to be acting up, may need investigation

Step 3 ✅ : bump react-native.

Looks like we're stuck on 0.76+ until react-native-macos catches up, as we need the main react-native and the out-of-tree react-native-macos platform to agree on their major version

Step 4 ✅ : bump all the lint stuff

Required some minor adjustments but nothing functional

Related issues

This should let us see what the original poster sees here:

• 🔥 update() with null does not remove the value from Firebase Database in iOS #8144

Release Summary

All the commits will be conventional commits, but none of them will be one of the keywords that triggers release, they'll all be build(deps) or chore

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
• 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

Lots and lots of testing. Currently step 1 passes local jest android and ios tests

Note: the functions tests disabled in the last commit need to be re-enabled and underlying issues fixed

---

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	Feb 5, 2025 4:16am

[russellwheatley]

LGTM. I guess next on the TODO is to fix functions package so we can unblock those e2e tests. Excellent work as ever, Mike 💯

[mikehardy]

@russellwheatley @MichaelVerdon

LGTM. I guess next on the TODO is to fix functions package so we can unblock those e2e tests. Excellent work as ever, Mike 💯

Thanks Russell - yeah, the very very next thing I'll do is immediately open a PR draft that has this as the base but reverts that commit and also brings your database test (which passes on old arch but should fail on new arch if the poster's information was accurate) - then we'll have all the new arch stuff at once. I think we'll all learn something figuring out why nulls are handled differently between old and new arch...

I don't feel proprietary about actually fixing it since I've got some other stuff cooking right now (Michael - you want to give it a shot?) but I can tee up the branch at least and then come back around to it in a few days if need be