[ci] use ubuntu-22.04 runner (#22797)

# Why

use the latest ubuntu runner and make ci more stable

# How

update to ubuntu-22.04 runner

Remove old expo-cli from workflows and test apps (#20998)

# Why

Fixes ENG-7251

This also allows us to move past Node 16 in the workflows.

# How

- Dropped unused `expo-cli` usage in workf

Remove old expo-cli from workflows and test apps (#20998)

# Why

Fixes ENG-7251

This also allows us to move past Node 16 in the workflows.

# How

- Dropped unused `expo-cli` usage in workflows
- Replaced all `expo-cli` commands with `npx expo` equivalents

# Test Plan

See if CI passes.

# 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 ...

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

[gh] Replace deprecated ::set-output (#19839)

[github] add local composite actions for CI, refactor workflows (#17162)

[github] always use `ubuntu-20.04` in workflows (#17051)

[github] update most of GitHub actions used in workflows (#17003)

[github] replace expo.io with expo.dev in URLs (#14709)

[workflows] update `setup-node` action (#14146)

[ci] Bump node version to 14.17

[ci] Add concurrency settings to all suitable workflows

[ci] Post GitHub comments from expo-ci account instead of github-actions

[github] Temporarily disable "Publish Expo Web" workflow, pending fixing deployment

[gha] Update cache action to v2 in all workflows

[ci] Fix NCL website deploy workflow

The secrets context is not available in if fields,
so before this commit the workflow would not run for
anyone.

After this commit, the workflow runs for all PRs

[ci] Fix NCL website deploy workflow

The secrets context is not available in if fields,
so before this commit the workflow would not run for
anyone.

After this commit, the workflow runs for all PRs that effect the related
files, but does not run the deploy steps if the PR author does not have
access to repository secrets.

show more ...

[ci] Don't use deprecated commands

Disable test when GH token isn't available (#10470)

[et] Add command that dispatches GitHub Actions workflows (#9732)

# Why

Easier way to dispatch workflow events to trigger them to run.

# How

- Added `et dispatch`/`et workflow-dispatch` com

[et] Add command that dispatches GitHub Actions workflows (#9732)

# Why

Easier way to dispatch workflow events to trigger them to run.

# How

- Added `et dispatch`/`et workflow-dispatch` command.
- Ensured `workflow_dispatch` is defined as a trigger in all our workflows.

# Test Plan

Some harmless examples to test:
- `et dispatch sdk` to check packages
- `et dispatch sdk-all` to check all packages (w/o incremental mode)
- `et dispatch shell-app-android` to build Android's shell app
- `et dispatch shell-app-ios` to build iOS shell app

show more ...

[ci] Use Node 14 and pin expo-cli to 3.x in web publishing tests (#8877)

Tests are failing because CI uses Node 13, which expo-cli doesn't support. This commit makes CI use Node 14. It also pins exp

[ci] Use Node 14 and pin expo-cli to 3.x in web publishing tests (#8877)

Tests are failing because CI uses Node 13, which expo-cli doesn't support. This commit makes CI use Node 14. It also pins expo-cli to 3.x in the web publish job so a future major version bump doesn't affect CI directly.

Testing by seeing if the web test suite job passes.

show more ...

[web][ci] Clone submodules

Without this the yarn.lock picks up changes.

[web][ci] Build PRs that touch the workflow file

[ci] Cache lfs objects

[tools] Remove expo-cli as a dependency of the workspace root (#8316)

Having expo-cli in the shared workspace dependency is preventing us from upgrading to TS 3.9 because it indirectly depends on TS

[tools] Remove expo-cli as a dependency of the workspace root (#8316)

Having expo-cli in the shared workspace dependency is preventing us from upgrading to TS 3.9 because it indirectly depends on TS 3.8. Specifically, expo-cli should not be pulling in TS. More generally, expo-cli indirectly depends on a lot of packages and Yarn workspaces + Metro are fragile when we have multiple dependencies with different versions. We've seen issues with multiple versions of Babel, React Navigation, and now TypeScript.

expo-cli was first added as a dependency of the root package.json along with the bin stubs. This was so that the whole repo was using the same version of Expo CLI. While I think this is very good, Having it be a dependency of the workspace root is problematic.

If we would like expo-cli installed and to restore the bin stubs, we could either make a separate dummy package that installs expo-cli or rely on a global copy and check its version. The important thing is that expo-cli is not a workspace dependency.

Looked through the CI config files and didn't see anything call into `expo`. Ran `expo --version` and ensured it matched the version of Expo CLI installed by expotools.

show more ...

[gh-actions] Disable native previews (#8112)

* Disable native previews

* Update app.json

Update web.yml