[tools] Switch expo home publishing to EAS update (#24216)

[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).

show more ...

Upgrade semver and json5 for remove security vulnerabilities (#23113)

# Why
Integrate Expo SDK in a bare flow project, creates new security
vulnerabilities.

![Screenshot 2023-06-26 at 9 52 16

Upgrade semver and json5 for remove security vulnerabilities (#23113)

# Why
Integrate Expo SDK in a bare flow project, creates new security
vulnerabilities.

![Screenshot 2023-06-26 at 9 52 16
AM](https://github.com/expo/expo/assets/10479750/590f3bae-e1e0-4452-9669-3aebb3641e0a)

This PR upgrade the Libs to remove those vulnerabilities


[CVE-2022-46175](https://www.mend.io/vulnerability-database/CVE-2022-46175)

[CVE-2023-0842](https://www.mend.io/vulnerability-database/CVE-2023-0842)
- It's already up to date

[CVE-2022-25883](https://www.mend.io/vulnerability-database/CVE-2022-25883)

[CVE-2022-25883](https://www.mend.io/vulnerability-database/CVE-2022-25883)

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How
It's a simple non-break changes lib upgrades
<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan
CI should pass
<!--
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.
This is required for changes to Expo modules.
-->

- [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)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Brent Vatne <[email protected]>

show more ...

[tools] Bump semver from 7.3.7 to 7.5.2 (#23042)

Update SwiftLint to 0.52.2 (#22801)

[et] migrate Fastfile release actions to EAS Build (#22426)

[tools] Add command to import accepted issues from GitHub to Linear (#22062)

# Why

In order to facilitate the management of SDK issues this PR proposes
automatically importing GitHub issues labe

[tools] Add command to import accepted issues from GitHub to Linear (#22062)

# Why

In order to facilitate the management of SDK issues this PR proposes
automatically importing GitHub issues labeled with the `issue-accepted`
tag to Linear, allowing us to better keep track of the status of each
individual issue, adding them to SDK projects, and centralizing internal
discussions in a single place.

Closes ENG-8130

# How

This PR introduces a new `et` command to import accepted issues from
GitHub to Linear, `et import-github-issue-to-linear` and also updates
the `issue-accepted` job of the `Issue Triage` workflow to run it every
time an issue is labeled as accepted.

To make the issue summary more concise and readable, this new command
uses GPT-4 to automatically summarize the problem described in the
GitHub issue, allowing team members to quickly skim through the text and
understand the issue.

Additionally, this new command attempts to infer a Linear user to assign
the issue by checking for users with the same full name, nickname, or
email address, in case a user was added as an assignee in the GitHub
issue.

Example of an issue automatically imported -> ENG-8187

# Test Plan

Run `et igitl --issue X` locally

# 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 `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[tools] Update @octokit/rest to 19.0.7

[android][tools] add sdk 48 versioned code (#21076)

# Why

add android sdk 48 versioned code

# How

- `et add-sdk -p android -s 48.0.0`
- there is a big problem for versioning this time wher

[android][tools] add sdk 48 versioned code (#21076)

# Why

add android sdk 48 versioned code

# How

- `et add-sdk -p android -s 48.0.0`
- there is a big problem for versioning this time where versioned aar size is from ~17MB to ~131MB because of prefab, so it's not able to commit to git. this pr proposes to upload versioned aar to github and having an `et android-download-versioned-aars` to download aars before gradle building.

# Test Plan

- sdk 48 android versioned expo go + sdk 48 ncl smoking test
- ci passed

show more ...

[tools] Adding "published" label to pull requests (#20840)

feat(expotools): use swc to compile source files (#20790)

# Why

- We use swc to compile Expo CLI, it's really fast.

## Before

`time yarn tsc` -- `14.22s`

## After

`time yarn build` --

feat(expotools): use swc to compile source files (#20790)

# Why

- We use swc to compile Expo CLI, it's really fast.

## Before

`time yarn tsc` -- `14.22s`

## After

`time yarn build` -- `0.67s`

> Over 21x faster.

# How

- Wrote a Taskr file that bundled the code similar to before. One very
notable difference is that type-checking is skipped.
- Not sure if the `patch`, `sh`, `jar`, `txt` files should be copied
into the build folder. Looks like they weren't being copied over with
tsc.

# Test Plan

- `yarn clean && yarn et -h`

show more ...

[github] use Node 16 for all workflows (#20803)

[tools][docs] TypeDoc update and related changes (#20687)

bump expo/expo-cli packages (#20720)

# Why

- security patches


<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

bump expo/expo-cli packages (#20720)

# Why

- security patches


<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

- add missing changelogs
- drop expo/json-file from metro-config

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

# Test Plan

- depending on automated tests

Co-authored-by: Expo Bot <[email protected]>

show more ...

[tools] Avoid dependency on uuid (#20478)

[workspace] bump and align TypeScript version (#20392)

[workspace] bump lint stack tools (#20387)

Update SwiftLint to 0.50.1 in code review CI action (#20238)

[tools][Android] Add android-update-native-dependencies command (#19960)

Co-authored-by: Bartłomiej Bukowski <[email protected]>

[tools] bump and clean up dependencies (#19076)

[tools] Lint Swift files in automatic code review (#15639)

Deprecate source-login-scripts.sh (#18330)

# Why

the `source-login-scripts.sh` introduced a lot of pain where the community reported much build errors from it. it doesn't support shells other tha

Deprecate source-login-scripts.sh (#18330)

# Why

the `source-login-scripts.sh` introduced a lot of pain where the community reported much build errors from it. it doesn't support shells other than zsh and bash. this pr find a new way to deal with xcode building issues that it cannot find the correct nodejs path.

close ENG-4864
close ENG-5242

# How

react-native introduces `.xcode.env` and `.xcode.env.local` for developers to override the `$NODE_BINARY`: https://github.com/facebook/react-native/pull/33546

to make sure building success from expo-constants, expo-updates, and also the app target when generating bundles. i would like to reuse the `.xcode.env` and `.xcode.env.local` from react-native. this pr further generates `.xcode.env.local` automatically for the app during `pod install`. we can ensure that `pod install` is executed from shell and nodejs is available. so we will generate `export NODE_BINARY="$(command -v node)"` in the `.xcode.env.local`. for xcode, the path will be `$PODS_ROOT/../.xcode.env.local`, every xcode subprojects can source the file to get correct `$NODE_BINARY`.

# Test Plan

- building bare-expo from xcode (opening xcode by macos finder)
- building bare-expo by `yarn ios`
- updates e2e ci passed
- building expo-go (prerequisite: #18344)

Co-authored-by: James Ide <[email protected]>

show more ...

[tools] update lint dependencies (#18340)

[expotool] improve generate-bare-app tooling (#17816)