mirror of
https://github.com/expo/eas-cli.git
synced 2026-11-15 17:31:46 -10:00
# Why The current release script requires that the user executing the script have permission to push changes to main without any PR requirement or checks. # How To allow us to add PR requirements and checks, I have added a manual GitHub workflow so that the existing script is executed by the expo-bot user, which is exempted from PR requirements. I have also made a few adjustments to the `release.yml` workflow (remove incorrect release name, update Node version to 22). # Test Plan - CI should pass - Try a release after this PR is merged
924 B
924 B
Releasing EAS CLI
- Invoke the GitHub workflow "Manually trigger a release". The next version is chosen automatically based on the changelog entries. If you want to use different version, pass the version string as an input to the workflow, in semver format, e.g. "1.2.3"
- That's it! GitHub Actions is going to take care of the rest. Watch the #eas-cli Slack channel for a successful release notification.
Choosing the next version
As stated above, the next EAS CLI version is chosen automatically based on the existing changelog entries under the unreleased section in CHANGELOG.md.
The algorithm works as follows:
- If there are any entries in the "🛠 Breaking changes" section, bump the MAJOR version.
- Otherwise, if there are any entries in the "🎉 New features", bump the MINOR version.
- Otherwise, bump the PATCH version.