* [ci] Version packages and generate changelogs with changesets
PRs now add a changeset in .changeset/ instead of editing CHANGELOG.md.
The manual release workflow runs scripts/src/versionPackages.ts, which
runs `changeset version` for one fixed group of all packages, writes the
root CHANGELOG.md section with the existing emoji categories, and then
commits, tags, and pushes vX.Y.Z. The tag-driven publish is unchanged,
except that it reads the changelog section from the tagged commit.
The PR check validates changesets with @changesets/parse and rejects
direct CHANGELOG.md edits. The "no changelog" label still skips it.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* Correct "no changelog" documentation in .changeset/README.md
* [ci] Fail on CHANGELOG.md edits even with the "no changelog" label
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [ci] Skip the changeset check for Dependabot PRs
Dependabot PRs only update dependencies, so they need no changeset, and
their read-only token cannot post the PR comment. The job skips both for
them. The CHANGELOG.md check still runs. The workflow now sets explicit
token permissions.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* Remove the "## main" block from CHANGELOG.md
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
* [eas-cli][local-build-plugin] Deprecate Node 20, use Node 22 in CI
Print a deprecation warning from the eas-cli and local-build-plugin
bin scripts when running on Node.js < 22. Develop and test on Node.js
22: bump mise, drop 20.18.3 from the test matrix, and move to
@tsconfig/node22 and @types/node 22. Published engines are unchanged.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
For better performance of the main test workflow, move ffmpeg-dependent tests to a separate workflow, with a restricted set of source files in the workflow trigger, and ensure that this workflow is not required for PRs.
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
- Rework the workflow so that the changelog is read correctly, and the changelog commit is skipped if the new entry is already present
- Split the npm check into its own release job and raise the timeout
- Serialize release runs with a concurrency group, effectively forcing them to queue
Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
* Update package.json to use new node version
* Update test workflow to use new node version
* Update important notes section in CLAUDE.md to use new node version
* Add changelog
# Why
We currently present Appium session events as HTTP methods which is not too human-readable (`getWindowRect`).
# How
Added a GHA workflow which runs weekly and submits a pull request adding to an `AppiumCommand` type so TSC fails and we need to add descriptions to commands.
# Test Plan
CI should pass.
# Why
Worker always fails to deploy when we release a new `eas-cli` version because the `latest` moves mid-run and NPM reports missing archive for the new version.
# How
Replaced `npx -y eas-cli@latest ...` calls with installing `eas-cli` globally once and then using `eas`.
# Test plan
Next `eas-cli` release should deploy worker ok.
# Why
Working on the repo locally, I found warnings and errors when linting workflows with actionlint.
# How
- Fix the warnings and errors, including updating a workflow using an outdated Node 20 runner.
- Add actionlint to the mise configuration, an actionlint script to the top level package.json, and an actionlint step in test.yml to ensure no regressions occur on future PRs.
# Test Plan
CI should pass, including the new actionlint check in test.yml.
# Why
Add `cli-versions.json` as the source of truth for the staging/production eas-cli versions, to remove the dependency on NPM tags to determine the correct version used in workflow jobs.
# How
Adding new function `fetchEasCliVersionsAsync` in the eas-build-job package. This reads the file from main on GitHub; build-tools uses it to build the eas-cli@<version> npx argument and falls back to the `latest-eas-build*` dist-tags on any failure. The release workflow now bumps cli-versions.json in the release commit and no longer posts the manual npm dist-tag reminder.
# Test Plan
New unit tests added.
* Refresh EAS CLI README
Co-Authored-By: Claude Fable 5 <[email protected]>
* Add changelog entry
Co-Authored-By: Claude Fable 5 <[email protected]>
* Link downloads badge to npm-stat instead of npmtrends
npmtrends.com/eas-cli currently returns a 500 on direct load.
Co-Authored-By: Claude Fable 5 <[email protected]>
* Trim social badge row from README header
Co-Authored-By: Claude Opus 4.8 <[email protected]>
* [eas-cli] Address README review feedback
Drop em dashes, link expo.dev/services instead of the redirecting
expo.dev/eas, bump the eas.json version example to >=21.0.0, drop the
retired Forums link, fix the 404ing dashboard link and the moved EAS
Submit docs URL, and note that README.md's header is generated.
Co-Authored-By: Claude Opus 5 <[email protected]>
---------
Co-authored-by: Claude Fable 5 <[email protected]>
- ECR_VERSION default ^0.2.0 -> ^0.2.1 (fuzzy quote-grounding + escalate-on-absence,
so real findings with imperfect quotes are no longer silently dropped).
- shared.md: ask for one contiguous verbatim line and drop the "evidence not found
-> discarded" threat, matching the engine's softened grounding behavior.
## Summary
- restore the quarterly Business Source License change-date workflow from `expo/eas-build`
- update `LICENSE-BUSL` instead of the former repository's root `LICENSE`
- run once when the workflow lands on `main`, then every three months
## Why
The EAS Build packages moved into this repository, but their scheduled BSL change-date automation was not moved with them. As a result, `LICENSE-BUSL` still has the last date written by the archived repository.
After this workflow lands on `main`, its path-based push trigger will advance the stale change date and future scheduled runs will keep it three years ahead.
The workflow deliberately does not run on pull requests because it uses the write-capable `EXPO_BOT_PAT`. Existing production evidence confirms that token can update the protected default branch: [`Release workflow` run 29394979387](https://github.com/expo/eas-cli/actions/runs/29394979387) successfully pushed `main -> main` on July 15, 2026 using the same repository secret.
## Validation
- `actionlint .github/workflows/license.yml`
- YAML parse check
- embedded Bash syntax check
- `git diff --check`
## Summary
Updates the codemention GitHub Action pin from `v1.4.0` to a reviewed post-`v1.5.2` upstream commit:
- `tobyhs/codemention@ebac5877393ab8693fd73b42708c8552043e9a3b`
- keeps the action pinned to an immutable commit SHA because this workflow runs on `pull_request_target` with `pull-requests: write`
- avoids pinning to moving `main` or a mutable tag
## Security review
I reviewed upstream `tobyhs/codemention` changes from `v1.4.0` through `v1.5.2` and found that `v1.5.2` introduced `[email protected]`, which currently has critical/high production dependency advisories. I therefore did not pin to `v1.5.2`.
The selected post-release commit includes follow-up dependency fixes on upstream `main`, including `[email protected]`, `[email protected]`, and `[email protected].0`. `npm audit --omit=dev` on that upstream commit reported 0 vulnerabilities at review time.
## Validation
- `yarn fmt:check .github/workflows/codemention.yml`
- YAML parse check
- `git diff --check`
# Why
There have been failures recently with the GitHub CHANGELOG check. Adjusting the workflow so that it can be manually tested.
# How
Add `workflow_dispatch:`
# Test Plan
CI should pass
* add skip-build-if-not-found to build:dev
* add changelog entry for build:dev skip flag
* Remove duplicate line in CHANGELOG
* Adjust CHANGELOG
* Bump add-pr-comment workflow dep
---------
Co-authored-by: Douglas Lowder <[email protected]>
## Why
In https://github.com/expo/eas-cli/pull/3406 EAS workflow building the worker was **not** updated to Yarn v4. This breaks building worker.
I tried adding `defaults.tools.yarn: 4.12.0`, but this unfortunately [is **not** the way to use Yarn v4 on EAS as I've learned](https://docs.expo.dev/more/create-expo/#yarn-2-modern). The right way is using Corepack.
However, previously we explicitly did **not** use Corepack, because `pnpm --version` check the worker does in the beginning of its run was failing because it was run without `cwd`, so it was running within worker package which was configured with Yarn.
Since we want to use Yarn v4, we need to figure out a way to use Corepack.
## How
- Enabled Corepack.
- Set up `yarn` executable like the one we have in `universe`.
- Changed `pnpm --version` to **not** run inside worker (so it does not error).
- Removed `setup-node` for specific Node versions in favor of a Mise override.
## Test plan
- Corepack + Yarn resolution checks (local):
- `mise exec [email protected].4 -- bash -lc 'corepack enable; yarn --version'` => `4.12.0`
- same check from `scripts/` => `4.12.0`
- Worker runtime unit test (local):
- `mise exec [email protected].4 -- bash -lc 'corepack enable; yarn workspace @expo/worker test:unit -- runtimeEnvironment.test.ts'`
- GitHub workflow runs:
- success on Corepack worker workflow update: https://github.com/expo/eas-cli/actions/runs/22133707462
- latest run for full set of changes: https://github.com/expo/eas-cli/actions/runs/22133932635
## Why
- Repository maintenance: standardize on Yarn 4 managed via Mise.
- Prepare for introducing minimum package-age constraints in dependency policy.
## How
- Migrated repo tooling to Yarn 4 with Mise.
- Updated CI and scripts for Yarn 4 behavior:
- Lerna invoked via `yarn run -T lerna`.
- Coverage args forwarded correctly (`-- --coverage`).
- Removed unsupported Yarn 4 `--silent` usage.
- Added missing package-local script dependencies surfaced by Yarn 4 (`jest`, `oxlint`, `rimraf`).
- Increased `EasCommand` coverage test timeout from 30s to 60s. (Was consistently failing in CI.)
## Test Plan
- CI only: `Run tests` matrix (including Node 20 coverage) and other touched workflows.
- Release behavior will be verified during the normal release run.
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
We're moving to Oxc in universe too. The toolset is faster than ESLint / Prettier.
# How
Asked Codex to migrate the repository. I don't think all rules got migrated, unfortunately, but also the lint are in a bit weird state (different rules in `eas-cli` vs the rest of the repo). I hope we can unify the rules soon.
# Test Plan
CI should pass.
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
Our GitHub released executable Oclif bundles of `eas-cli` are… not too popular. v16.28.0 was downloaded 154k times in the last 7 days from NPM. Since its release (2 months ago) it was downloaded from GitHub 82 times.
<img width="1247" height="491" alt="Zrzut ekranu 2026-01-30 o 15 15 35" src="https://github.com/user-attachments/assets/9c5a904a-e00e-43ee-9875-d1cea15b2108" />
# How
Asked Gemini to remove this. This should speed up release process significantly. This release process has been created 5 years ago (https://github.com/expo/eas-cli/pull/54).
Also removed size comparison workflow. It's not going to make comments like https://github.com/expo/eas-cli/pull/3361#issuecomment-3824036144.
Closes https://github.com/expo/eas-cli/pull/3346.
# Test Plan
CI should pass.
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
I noticed I didn't migrate all workflows to Mise (because not all worklfows were using Volta lol).
# How
Codex added a shared Mise action (in other repos we have it set up like this too) and used it in all places where we require Node related to code (there's one workflow which does not use checkout, it remains on `setup-node` too). `test.yml` where we test against different Node versions still uses `setup-node`.
Note: this does downgrade Node in a few workflows from 22 to 20, but if 20 is what we decide to use for our development maybe CI should use it too?
# Test Plan
CI should pass.
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
I think we migrated from Volta to Mise in… most if not all places?
# How
I think I let Codex do all the work, nothing too difficult. Grepped repo for "volta" leftover afterwards.
One thing I'm not sure of is whether worker is going to work. I remember trying to remove Volta in `turtle-v2` and it wasn't working for some reason? We'll see.
# Test Plan
Compared these changes with https://github.com/expo/universe/commit/acca8169746c5cb4d708add083f77b927341ae4a.
<!-- If this PR requires a changelog entry, add it by commenting the PR with the command `/changelog-entry [breaking-change|new-feature|bug-fix|chore] [message]`. -->
<!-- You can skip the changelog check by labeling the PR with "no changelog". -->
# Why
We moved more packages into this monorepo and the existing test setup didn’t scale well:
- the root Jest config only covered a subset of packages,
- PRs ran heavier “all tests” workflows,
- worker builds ran on PRs even though typecheck + tests were enough.
This PR aligns testing with the dependency graph, reduces unnecessary CI work, and standardizes Jest config handling.
# How
- Switched root testing to Lerna and updated docs.
- CI now runs affected+dependent tests on PRs and all packages on main.
- Coverage runs via Lerna with per-package reports (no merge) and is kept for PRs.
- Worker builds are skipped on PRs; worker workflow triggers include dependency paths on main.
- All Jest configs are now TypeScript with a shared base (`jest/jest.shared.config.ts`) and use `@jest/types` to avoid TS config parsing errors.
- CI stays unit-only (no integration tests).
# Test Plan
Not run locally. CI covers:
- `yarn lerna run test` (affected on PRs, all on main)
- `yarn lerna run test -- --coverage`
`package.sh` currently does not copy workspace packages into the temporary build folder which makes worker pull packages from NPM.
Instead, we want to use local versions from workspace.
Added `copy_package` calls for all dependencies of `@expo/worker`.
It was done in a similar way in `turtle-v2` — https://github.com/expo/turtle-v2/blob/245eaf23492f2dcd9204a4606bb95c109208d29e/src/services/worker/package.sh#L46-L47.
Ran `./package.sh` and confirmed `@expo/eas-build-job` and other packages are symlinked.
## Why
The build-and-deploy-worker workflow had three separate jobs (setup, build-workers, deploy) with complex inter-job dependencies and redundant conditional logic. I think if we put it all in one job it should make stuff faster.
## How
Consolidated all three jobs into a single `build-and-deploy` job with conditional steps:
1. **Check**: Verify if tarballs for the current SHA exist in GCS (when deploying)
2. **Build**: Execute EAS workflow if needed (PR testing or cache miss)
3. **Upload**: Upload tarballs to GCS with SHA-based naming
4. **Deploy**: Copy tarballs to environment-specific names (when deploying)
Key simplifications:
- **Assumption**: Main branch always specifies an environment (staging/production), so `environment == ''` only occurs on PR builds
- **SHA-based caching**: Check cache by SHA regardless of branch - if the code is identical (same SHA), reuse existing tarballs
- **Clearer conditions**: Each step has a single clear purpose without overlapping branch-specific logic
I also added back building Linux tarball on Linux not to mix CPU architectures accidentally.
## Test Plan
[Build on PR](https://github.com/expo/eas-cli/actions/runs/20920297113/job/60104039095?pr=3303). [Deployment from a branch](https://github.com/expo/eas-cli/actions/runs/20921082109/job/60106516235).
Co-authored-by: Claude <[email protected]>