* [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]>
2.4 KiB
Development
Getting Started
If this is your first time running eas-cli locally, make sure you install and build the packages. In the project root, run:
yarn install
yarn build
From there, set up an alias for the EAS CLI so you can try it in projects all around your computer. The project is compiled on the fly so you don't need to run a build (watch) command.
The only exception is if there have been changes in
packages/eas-json. In that case, you'll have to runyarn buildin the root.
Open your .zshrc or other config file and add:
alias easd="/PATH/TO/eas-cli/bin/run"
Then use it with easd like easd build.
If you're making changes to packages/eas-json or prefer/need to work with production code, start the build command in watch mode with:
yarn start
If it is easier for you to work with the code locally with compiler options set to:
...
"compilerOptions": {
...
"noUnusedLocals": false,
"noUnusedParameters": false,
...
}
...
you can consider using:
yarn start-allow-unused
Format
- Add a changeset for every PR that changes a package: run
yarn changesetand commit the new file. Do not editCHANGELOG.md; the release generates it. See.changeset/README.md. - End
asyncfunctions withAsynclikerunAsync. This is just how we format functions at Expo. - Utilize the unified
Logmodule instead ofconsole.log.
Using local and staging API
For development against local API:
- Set up the API server as described at https://github.com/expo/universe/tree/main/server/www.
- Set the
EXPO_LOCAL=1env variable either on every command run (e.g.EXPO_LOCAL=1 easd ...) or more permamently withexport EXPO_LOCAL=1(works in a current shell session).
For development against staging API:
- Set the
EXPO_STAGING=1env variable either on every command run (e.g.EXPO_STAGING=1 easd ...) or more permamently withexport EXPO_STAGING=1(works in a current shell session).
Working on local builds (eas build --local)
See CLAUDE.md for how to set up your environment when making changes to eas-cli-local-build-plugin and/or build-tools.
Testing
From the repository root, run yarn run -T lerna run test. For a single package, run yarn test in that package directory.
Releasing
See RELEASING.md.