build(deps): dependency updates 20260811 - #9190
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9190 +/- ##
============================================
+ Coverage 68.13% 68.17% +0.05%
+ Complexity 1915 1914 -1
============================================
Files 511 511
Lines 37888 37904 +16
Branches 5197 5200 +3
============================================
+ Hits 25810 25838 +28
+ Misses 10250 10236 -14
- Partials 1828 1830 +2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
mikehardy
left a comment
There was a problem hiding this comment.
the expo plist one is specifically amusing to me because I wrote somewhere (I thought this okf-bundle for RNFB!) that if dependencies were updated they should always be the most up to date
I don't know why but apparently a new / modern "classic" is that agents never grab the most up to date version when they add or move dependencies. It is always some stale version
Also, dependabot itself is limited on how many things it proposes at once and was down on the repo for a while, now that it's back up they really are coming in seemingly unending waves but hopefully they all go through shortly and the queue is empty
Combines open Dependabot
build(deps)PRs onto one branch.Included
actions/setup-java5.6.0 → 5.7.0guidepup/setup-action0.20.0 → 0.21.0reactivecircus/android-emulator-runner2.37.0 → 2.38.0ruby/setup-ruby1.313.0 → 1.321.0@expo/plist0.5.2 → 0.8.1 (auth Expo config plugin)Intentionally skipped
react/@types/react) — cannot upgrade React in this tree right nowNote on #9187
#9171 only SHA-pinned
android-emulator-runnerwithin v2.37.0. This PR takes Dependabot's follow-up bump to v2.38.0 (build-tools 37). The red checks on #9187 were unrelated to that pin: conventional-commit title vs commit-subject mismatch, plus an iOS SPM flake on a GitHub TLS cert during checkout.Obsoletes