[tools] Add publish-prod-home command (#24432)
[tools] Remove classic publishing for apps (#24345)
[tools] Switch expo home publishing to EAS update (#24216)
chore!(expo-splash-screen): Delete deprecated `hide` and `preventAutoHide` methods. (#24296)# Why - These methods have been deprecated for years. - The default native module (web) mocks all met
chore!(expo-splash-screen): Delete deprecated `hide` and `preventAutoHide` methods. (#24296)# Why - These methods have been deprecated for years. - The default native module (web) mocks all methods, this means the unavailability errors cannot be thrown. As such, I dropped them. - Dropped the extra layers of re-exporting code. These add bundling time and not much else. - Dropped the tests as they weren't testing anything. --------- Co-authored-by: Expo Bot <[email protected]>
show more ...
[tools] Temporarily disable issue comments on publish [skip ci]
[home][ci] Remove dogfood expo home variant (#24193)
[home][tools] Fix detecting home app for dynamic macros (try 2) (#24189)
[ci][tools] fix react-native 0.73 compatibility [3/3] (#24020)# Why fix react-native 0.73 compatibility. this pr focus on fixing ci test-suite-nightlies. # How - [ci] use node 18 and jdk 1
[ci][tools] fix react-native 0.73 compatibility [3/3] (#24020)# Why fix react-native 0.73 compatibility. this pr focus on fixing ci test-suite-nightlies. # How - [ci] use node 18 and jdk 17 which are required from 0.73 - [ci] use `npx pod-install` rather than `pod install` and fix hermes-engine podfile.lock update issue - [tools] update SetupReactNativeNightly script # Test Plan ci passed in #23961 (https://github.com/expo/expo/pull/23961/checks)
[ci] try to improve ci stability (#24002)# Why try to improve ci stability # How - android-unit-tests - prevent timeout and out of disk space - client-android-eas - since client-and
[ci] try to improve ci stability (#24002)# Why try to improve ci stability # How - android-unit-tests - prevent timeout and out of disk space - client-android-eas - since client-android is not stable, try to broad the client-android-eas path coverage - for external contributors (forked repo), just ignore the workflow - client-ios-eas - for external contributors (forked repo), just ignore the workflow - client-android - TBD - client-ios - remove s3 and store publish - ios-unit-tests - prevent timeout - clipboard - fix timeout issue because of slow NSAttributedString html processing - `et dispatch`: remove unused workflows - releasing guide: update to the newer `et eas` releasing workflows # Test Plan ci passed
[go] update lottie-react-native to 6.1.2 (#23843)# Why There have been a lot of changes in Lottie React Native and there are some issues for users using Expo Go. May fix: - https://github.c
[go] update lottie-react-native to 6.1.2 (#23843)# Why There have been a lot of changes in Lottie React Native and there are some issues for users using Expo Go. May fix: - https://github.com/lottie-react-native/lottie-react-native/issues/1075 - https://github.com/lottie-react-native/lottie-react-native/issues/999 - https://github.com/lottie-react-native/lottie-react-native/issues/1005 # How - Changed source type to `npm` in expoGoConfig - Ran `et uvm -m lottie-react-native -c 6.1.2` - Updated NCL example # Test Plan versioned expo go + NCL lottie test case --------- Co-authored-by: Kudo Chien <[email protected]>
Remove `exp-artifacts` bucket mention (#23842)# Why We want to remove `exp-artifacts` bucket since Turtle v1 is no longer running. # How Removed `S3.ts` which seems to no longer be used. S
Remove `exp-artifacts` bucket mention (#23842)# Why We want to remove `exp-artifacts` bucket since Turtle v1 is no longer running. # How Removed `S3.ts` which seems to no longer be used. See https://github.com/expo/universe/pull/11975#issue-1657508370. # Test Plan Ran `yarn build`, `yarn tsc --noEmit` in `src/tools`. Both succeeded, which, to me, means the file wasn't used.
delete expo-stories (#23760)# Why - `expo-stories` is unmaintained and unused. - The dependency on react-navigation is blocking the expo-router migration https://github.com/expo/expo/pull/2372
delete expo-stories (#23760)# Why - `expo-stories` is unmaintained and unused. - The dependency on react-navigation is blocking the expo-router migration https://github.com/expo/expo/pull/23725 because there are no maintainers it's unclear how to safely upgrade react-navigation in stories.
[tools] sync VERSION_EMPTY_PARAGRAPH_TEXT changelog (#23729)# Why fix the problem that `sync-sdk-branch-changelogs` does not sync changelog for `_This version does not introduce any user-facing
[tools] sync VERSION_EMPTY_PARAGRAPH_TEXT changelog (#23729)# Why fix the problem that `sync-sdk-branch-changelogs` does not sync changelog for `_This version does not introduce any user-facing changes._` # How the `_This version does not introduce any user-facing changes._` item is not in list form so that the `Changelogs.getChangesAsync()` does not count it into totalCount. this pr ignores the `totalCount` and merge the changelogs anyway. # Test Plan run `et ssbc -b sdk-49` and see if the **packages/expo/CHANGELOG.md** is updated
[tools] fix hermes inspector error from versioning
[tools] Bump word-wrap from 1.2.3 to 1.2.4 (#23612)Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
[tools] Fix detecting home app for dynamic macros (#23583)
[core][Android] Fix instrumented tests (#23336)# Why Fixes instrumented tests can't be run from the `bare-expo` project. # How While dealing with another issue, I came across a problem - I
[core][Android] Fix instrumented tests (#23336)# Why Fixes instrumented tests can't be run from the `bare-expo` project. # How While dealing with another issue, I came across a problem - I couldn't run instrumented tests from the `bare-expo` project. After some investigation, I discovered that Hermes was misconfigured. I realized that Hermes should be added by prefabs, so I removed the logic responsible for downloading it. Although I'm not entirely certain if it's entirely safe, I performed a clean build and everything seemed to work correctly. cc @Kudo # Test Plan - bare-expo ✅ - instrumented tests ✅
[expo-tools] Check for unused transforms for vendored code. (#22938)
[core] Add uuid to expo-modules-core (#23249)
[workspace] Bump TypeScript version to 5.1.3 (#23143)# Why Closes ENG-9088 # How Bump TypeScript to the latest, and rebuild all required SDK packages Had to update `typeRoots` inside `
[workspace] Bump TypeScript version to 5.1.3 (#23143)# Why Closes ENG-9088 # How Bump TypeScript to the latest, and rebuild all required SDK packages Had to update `typeRoots` inside `expo-module-scripts` due to a change in TypeScript 5.1 where it no longer walks up automatically looking in parent directories ([Release notes](https://devblogs.microsoft.com/typescript/announcing-typescript-5-1-rc/#typeroots-are-consulted-in-module-resolution)) # Test Plan Ensure that `et cp -a` yields no errors, docs and tools build correctly, and that CI is green # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] 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).
chore: update react-native to 0.72.1 (#23262)# Why update react-native 0.72.1 for sdk 49 # How - bump react-native to 0.72.1 - re-version android/ios sdk 49 code - [react-native-lab] che
chore: update react-native to 0.72.1 (#23262)# Why update react-native 0.72.1 for sdk 49 # How - bump react-native to 0.72.1 - re-version android/ios sdk 49 code - [react-native-lab] cherry-pick necessary commits between 0.72.0..0.72.1 # Test Plan - ci passed - bare-expo - versioned expo go
[tools] Allow for package-specific transforms in versioning script (#23227)
[go] update @shopify/react-native-skia to 0.1.196 (#23157)# Why 0.1.196 is the first version compatible with react-native 0.72, we need this version for sdk 49 # How - `et uvm -m @shopify/
[go] update @shopify/react-native-skia to 0.1.196 (#23157)# Why 0.1.196 is the first version compatible with react-native 0.72, we need this version for sdk 49 # How - `et uvm -m @shopify/react-native-skia -c 0.1.196` - re-add sdk49 versioned code for skia # Test Plan - [x] unversioned expo-go + unversioned ncl skia test case - [x] sdk49 versioned expo-go + sdk49 ncl skia test case - [x] ios expo go (2.29.1, the current testflight version, which is @shopify/[email protected]) + sdk49 ncl skia test case (@shopify/[email protected]). this test makes sure 0.1.196 doesn't have breaking changes and compatible with 0.1.195, so that we don't have to submit a new expo-go build.
[ios][updates][tools] fix swift casting runtime exception (#23132)# Why close ENG-9094 # How - this is again the swift runtime exception for casting versioned class to unversioned class li
[ios][updates][tools] fix swift casting runtime exception (#23132)# Why close ENG-9094 # How - this is again the swift runtime exception for casting versioned class to unversioned class like https://github.com/expo/expo/pull/23012#discussion_r1237294135. this time it's the `EXUpdatesUpdate` and solved by the `object_setClass` too. - moving the `object_setClass` to expo-go only `EXUpdatesBinding` class which is a proper place to do the casting. however, this requires more swift <-> objc interop like adding swift compatibility header to search paths and adding `-fmodule-map`. - some refactoring for the expokit podspec # Test Plan - ci passed - test local expo-go to load sdk 49 updates (both classic updates and eas updates)
[go] add android sdk49 versioned code (#23110)# Why for sdk 49 # How - [go] add android sdk 49 versioned code - [tools] minor fix for android versioning # Test Plan ci passed
12345678910>>...36