Skip to content

Bump lodash from 4.17.21 to 4.17.23 in /tools#12

Closed
dependabot[bot] wants to merge 513 commits into
mainfrom
dependabot/npm_and_yarn/tools/lodash-4.17.23
Closed

Bump lodash from 4.17.21 to 4.17.23 in /tools#12
dependabot[bot] wants to merge 513 commits into
mainfrom
dependabot/npm_and_yarn/tools/lodash-4.17.23

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Jan 26, 2026

Bumps lodash from 4.17.21 to 4.17.23.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

alanjhughes and others added 30 commits January 22, 2025 18:37
expo-camera@16.0.14
)

# Why

I need to see if an android contact is starred or not.

# How

I modified the code under expo-contacts to support starred.

# Test Plan

I added an official test for it, but I also manually created contacts on
the android device and ensured I get starred true and false properly.
 
# Checklist

- [x] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

I don't know what this last checklist item is... Can someone clarify?

---------

Co-authored-by: Vojtech Novak <vonovak@gmail.com>
# Why

sdk-52 ios CI fails

# How

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
-->

- [ ] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
…ty. (expo#34474)

Automatically skip networking when running in a webcontainer

---------

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
…AN ip (expo#34368)

# Why

Fixes expo#33833

Right now, React Native DevTools is a forked Chrome DevTools maintained
by Meta and shipped as package within `@react-native/dev-middleware`.
This means React Native DevTools is both versioned per Expo SDK/React
Native version, as well as hosted locally from the development machine
itself.

Previously, we always bind this debugging infrastructure to the LAN IP
of the development machine. Unfortunately, this doesn't always work,
especially on restricted corporate networks where every individual
machine connected to the network can't be accessed, even from the same
development machine.

# How

This changes the debugging infrastructure to always bind to localhost.
Note that this does not affect `expo start`, which will still bind to
any IP including LAN by default to allow opening the project on
LAN-connected Expo Go or dev clients.

# Test Plan

- `bun create expo ./test-debugging`
- `cd ./test-debuggin`
- `bun expo start`
- `curl http://localhost:8081/json/list | jq` should show websocket
connections coneccting to `..://localhost:8081/...`.
- Press `j` in terminal should open React Native DevTools, even on
restricted networks/offline

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
-->

- [ ] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
regression from expo#33348 that delegate methods from AppDelegate.mm are not
be called

When using AppDelegate.mm, the `self` in ExpoAppInstance is not the true
AppDelegate.mm, since the hierarchy is

```
AppDelegate.mm -> derive from ExpoAppDelegateWrapper -> composite ExpoAppInstance
```

where in AppDelegate.swift it's

```
AppDelegate.swift -> derive from ExpoAppDelegate -> derive from ExpoAppInstance
```

to make AppDelegate.mm case works, we pass the true AppDelegate to
ExpoAppInstance and call it when it's available.

- test `expo@52.0.27` with react-native-bootsplash and add a break point
at `customizeRootView`
- ci passed

- [x] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

---------

Co-authored-by: Vojtech Novak <vonovak@gmail.com>
add experimental libsql integration
close ENG-14210

- add my prebuilt libsql.xcframework with dynamic frameworks and prevent expo-updates crash
- copy `SQLiteModule.swift` to `SQLiteModuleLibSQL.swift` and update to use libsql c bindings
- add config-plugin to update Podfile.properties.json

---------

Co-authored-by: Alan Hughes <30924086+alanjhughes@users.noreply.github.com>
(cherry picked from commit 425d4ad)
close ENG-14210

add libsql integration in cpp level

(cherry picked from commit 4054118)
expo-task-manager@12.0.5
expo-sqlite@15.1.0
expo-notifications@0.29.13
expo-modules-core@2.2.0
expo-maps@0.7.0
expo-linking@7.0.5
expo-dev-launcher@5.0.26
expo-contacts@14.0.4
expo-constants@17.0.5
expo-background-task@0.1.0
expo-background-fetch@13.0.5
expo@52.0.28
@expo/cli@0.22.11
fix the wrong xcframework lib

use `install_name_tool` to replace the rpath

testing on brent's machine

- [x] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
expo-sqlite@15.1.1
…xpo#34220)

# Why

We're looking to adopt `@expo/fingerprint` at PlayerData, but we've been
tripped up by `.gitignore` changes showing a diff in the fingerprint.

While I can appreciate that some changes to `.gitignore` may result in
changes, the vast majority should be safe (particularly in a CNG
project).

# How

This PR adds a `SourceSkips.GitIgnore` option that users can opt-in to.

(cherry picked from commit bac84f4)
On Android, when saving a contact that has a photo attached to it, the
method will fail because we're not resolving the path to the photo
correctly (not using a content resolver).

Note: This was previously solved in expo#32097 by
[freeboub](https://github.com/freeboub) - thanks!

- Added using contentResolver to get the correct inputstream to the
photo in the Contact class
- Passed appContext from Contacts module to be able to use the
contentResolver
- Added support for testing saving an image (ie. changing picture) on
Android in BareExpo

Closes #ENG-14832

Test in BareExpo:
- Open Contacts test screen
- Click contact image and select a new image (this will save the
contact)
- Verify that the contact was successfully saved.

- [x] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Co-authored-by: Łukasz Kosmaty <lukasz.kosmaty@swmansion.com>
…xpo#34431)

The package `expo-background-task` was just recently merged into `main`.
This PR follows up on expo#34176 to add support for the new expo modules
gradle plugin.

Updated build.gradle with new pattern.

✅ BareExpo

- [x] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
…em again during updateContactAsync (expo#34186)

updateContactAsync corrupts contact:
- update contact without website (to remove it) => the website field is
not deleted
- update contact with two website => only one website field is returns

The modified loop was not good. on each field it add 1 delete request
and 1 add request.
--> if user wants to remove a field, the delete is not added => field
remains in database
--> if user wants to add multiple a field, the delete is not added on
each loop => first loop add delete and Add, second loop add delete and
add then the second delete will remove data added by by the first add.

Solution:
flush all fields before creating the new add requests

2 new tests were added to the test suite

- [x] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

---------

Co-authored-by: Olivier Bouillet <olivier@azzapp.com>
# Why 

When an app is terminated there are some limitations on Android and iOS
when it comes to background location.

# How

This update tries to clarify these changes a bit.

Updated both `unversioned` and `sdk-52`

# Checklist

- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

---------

Co-authored-by: Aman Mittal <amandeepmittal@live.com>
#Why 

There are some differences on iOS/Android when it comes to permissions.

# How

This commit clarifies these.

- Updated location.mdx in both `unversioned` and `sdk-52`

Closes expo#33911

# Checklist

- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

---------

Co-authored-by: Aman Mittal <amandeepmittal@live.com>
alanjhughes and others added 21 commits April 10, 2025 19:42
…dling for channel filtering during updates
…es for improved channel switching in selection policy
…annel switch debugging

Logs the following information when selectUpdateToLaunch is called:
- filterByChannel flag value
- config.requestHeaders (should contain expo-channel-name)
- config.disableAntiBrickingMeasures value
- Total and eligible update counts
- Each update's branch vs target channel comparison
- Final selection result

This will help identify why channel switching is not working as expected.

Bump version to 0.0.12.
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.21 to 4.17.23.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.21...4.17.23)

---
updated-dependencies:
- dependency-name: lodash
  dependency-version: 4.17.23
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jan 26, 2026
@github-actions
Copy link
Copy Markdown

Subscribed to pull request

File Patterns Mentions
tools/** @tsapeta

Generated by CodeMention

@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github Feb 11, 2026

Looks like lodash is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Feb 11, 2026
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/tools/lodash-4.17.23 branch February 11, 2026 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.