-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Comparing changes
Open a pull request
base repository: invertase/react-native-firebase
base: v23.7.0
head repository: invertase/react-native-firebase
compare: v23.8.0
- 20 commits
- 273 files changed
- 5 contributors
Commits on Dec 8, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 21c1402 - Browse repository at this point
Copy the full SHA 21c1402View commit details -
chore(release): attempt shell unset syntax for npm token
back to actual tokens vs OIDC trusted publish if this doesn't work I suppose
Configuration menu - View commit details
-
Copy full SHA for 1abc0da - Browse repository at this point
Copy the full SHA 1abc0daView commit details -
chore(release): if node registry-url is omitted, NODE_AUTH_TOKEN shou…
…ld be as well those code paths are dependent in actions/setup-node
Configuration menu - View commit details
-
Copy full SHA for 5d81556 - Browse repository at this point
Copy the full SHA 5d81556View commit details -
chore(release): use token-based npmjs publish for now
Temporarily admitting defeat on tokenless OIDC Trusted Publish It was working, then stopped working approximately Nov 27. Why? Unknown but I know a lot of reasons how it can not work now.
Configuration menu - View commit details
-
Copy full SHA for 4673035 - Browse repository at this point
Copy the full SHA 4673035View commit details -
chore(release): npm auth token requires setting registry-url for node…
…-setup as discovered before, that's how the .npmrc with auth config is written and apparently without that things still don't work
Configuration menu - View commit details
-
Copy full SHA for 2a30c0b - Browse repository at this point
Copy the full SHA 2a30c0bView commit details
Commits on Dec 9, 2025
-
feat(functions): turbo modules implementation (#8603)
Co-authored-by: Mike Hardy <github@mikehardy.net>
Configuration menu - View commit details
-
Copy full SHA for ad09a9b - Browse repository at this point
Copy the full SHA ad09a9bView commit details -
fix(messaging, types): isSupported signature should be `Promise<boole…
…an>` not `boolean` (#8798)
Configuration menu - View commit details
-
Copy full SHA for 4d54636 - Browse repository at this point
Copy the full SHA 4d54636View commit details
Commits on Dec 17, 2025
-
Configuration menu - View commit details
-
Copy full SHA for dc28a77 - Browse repository at this point
Copy the full SHA dc28a77View commit details
Commits on Dec 18, 2025
-
refactor: improved exported types and updated type-tests.ts, intellis…
…ense now works (#8809)
Configuration menu - View commit details
-
Copy full SHA for 7e064cf - Browse repository at this point
Copy the full SHA 7e064cfView commit details
Commits on Dec 19, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 804508b - Browse repository at this point
Copy the full SHA 804508bView commit details
Commits on Dec 29, 2025
-
fix(app): firebase-ios-sdk 12.7.0 / firebase-js-sdk 12.7.0 (#8810)
Update both the native iOS SDK and the JS SDK to their recent 12.7.0 versions In particular this allows the JS sdk to move it's dep (and our transitive dep) of react-native-async-storage to the v2.x series for react-native new architecture compatibility in react-native-firebase library consumers
Configuration menu - View commit details
-
Copy full SHA for e00bd87 - Browse repository at this point
Copy the full SHA e00bd87View commit details
Commits on Jan 2, 2026
-
chore(ci): only cache main - avoid branches LRU evicting main cache
use the separate actions/cache "restore" and "save" actions so we may only save optional based on whether we are on main or not actions/cache isolates branch caches from main to avoid branch cache poison attacks on main runs but branches may see main cache as those caches are considered trustworthy branch caches do consume available LRU storage though, meaning branch caches could evict main caches and in high traffic / large cache repositories like this one that means caches LRU out frequently and cache hit rates are terrible unless you cache on main only
Configuration menu - View commit details
-
Copy full SHA for 0b14ccb - Browse repository at this point
Copy the full SHA 0b14ccbView commit details -
chore(ci): cache restore/save failures should never break the build
very occasionally, there are errors in the `hashFiles` function used to calculate cache keys, and this causes a build error that is a flake, not a valid CI failure signal so, continue the workflow even if the caching setup has errors, as that is a recoverable problem and the workflow may still have a valid success outcome
Configuration menu - View commit details
-
Copy full SHA for 83c18b1 - Browse repository at this point
Copy the full SHA 83c18b1View commit details -
chore(ci): firebase emulators are cross-platform, share cache across OSs
the downloaded/cached files are pure javascript and java, they may be shared across operating systems safely
Configuration menu - View commit details
-
Copy full SHA for 8dbc5ba - Browse repository at this point
Copy the full SHA 8dbc5baView commit details
Commits on Jan 5, 2026
-
feat(firestore): add VectorValue type and vector() API
- modular API only we are no longer adding namespaced-functionality - supported usage is to create with `vector` or `fromJSON`, serialize w/toArray() Co-authored-by: Mike Hardy <github@mikehardy.net>
Configuration menu - View commit details
-
Copy full SHA for 8de9b68 - Browse repository at this point
Copy the full SHA 8de9b68View commit details -
perf(ci): only save ccache on main branch
prevents LRU eviction thrashing of caches since we are near the limit on useful caches for a single CI run
Configuration menu - View commit details
-
Copy full SHA for a2844d4 - Browse repository at this point
Copy the full SHA a2844d4View commit details
Commits on Jan 8, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 43081df - Browse repository at this point
Copy the full SHA 43081dfView commit details -
Configuration menu - View commit details
-
Copy full SHA for 98b4d79 - Browse repository at this point
Copy the full SHA 98b4d79View commit details -
Configuration menu - View commit details
-
Copy full SHA for e16ccc4 - Browse repository at this point
Copy the full SHA e16ccc4View commit details
Commits on Jan 13, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 724ddcf - Browse repository at this point
Copy the full SHA 724ddcfView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v23.7.0...v23.8.0