Bump graphql from 16.3.0 to 16.8.1#5
Closed
dependabot[bot] wants to merge 511 commits into
Closed
Conversation
# Why - I needed this for a side-project (https://pillarvalley.expo.app) - App Clips are weird in how they handle deep links. The don't call the open: function so we need to use the continue user activity function. This could lead to a weird edge case where the app clip was launched without a URL (maybe an advanced invocation) then later visited with a URL, which would be treated as the initial URL at that point. # How - Implement the missing expo-linking AppDelegate function which we need regardless as it is invoked for subsequent URL changes and NSUserActivities. - Add a simple check for if running in an app clip. - Add the nullish URL check that can cause fatal RN crashes. I've upstreamed this change to RN already. # Test Plan - Run in an App Clip with `_XCAppClipURL` env var set in the Xcode configuration for the build. The URL cannot be the Apple default `https://appclip.apple.com/id?p=com.evanbacon.pillarvalley.clip` as this will trigger a crash due to some bug in Xcode. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
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>
expo-dev-menu@6.0.25 expo-dev-launcher@5.0.35 expo-dev-client@5.0.20 expo@52.0.44
…simulator (expo#36060) # Why The previous fix found here: expo#36044 - was a bit too strict. # How This commit fixes this by changing it so that we handle the specific scenario where the check actually works (on previous versions) and we can display the dialog. # Test Plan See expo#36044 for details. # Checklist - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
…even without embedded update
…ynamic configuration resolution
…pdates by channel/branch
…annel filtering during updates
…dling for channel filtering during updates
Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-version: 16.8.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Subscribed to pull request
Generated by CodeMention |
Author
|
Looks like graphql is up-to-date now, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps graphql from 16.3.0 to 16.8.1.
Release notes
Sourced from graphql's releases.
... (truncated)
Commits
8a9533516.8.18f4c64eOverlappingFieldsCanBeMergedRule: Fix performance degradation (#3967)e4f759d16.8.0bec1b49Support fourfold nested lists (#3950)bf6a9f016.7.1a08aaeeinstanceOf: workaround bundler issue withprocess.env(#3923)1519fda16.7.084bb146check "globalThis.process" before accessing it (#3887)076972eFix/invalid error propagation custom scalars (backport for 16.x.x) (#3838)4a82557Fix crash in node when mixing sync/async resolvers (backport of #3706) (#3707)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.