mirror of
https://github.com/expo/eas-cli.git
synced 2026-11-15 17:31:46 -10:00
There was no way to ship a version for people to try. Running the existing release with a prerelease version would have been actively harmful: `lerna publish from-package` passed no --dist-tag and npm has not special-cased prerelease versions since v7, so `latest` would have pointed at the prerelease and every `npx eas-cli` user would have gotten it. The run would also have moved `latest-eas-build` and `latest-eas-build-staging` — which select the CLI version for EAS Build, so a prerelease would have reached production builds — and consumed the unreleased CHANGELOG.md section, committing it to main and Slack-announcing it as a release. The stale `next` (7.1.0) and `alpha` (0.16.1-alpha.0) dist-tags show how long it has been since anyone tried. Detect a SemVer prerelease identifier on the pushed tag and branch on it: publish under `next`, skip both EAS Build dist-tag steps, and skip the changelog job so the entries stay unreleased for the stable release that follows. The GitHub release is published immediately and flagged as a prerelease instead of waiting for the changelog job to un-draft it. The dist-tag is now always passed explicitly. `latest` is what npm defaulted to, so stable releases are unchanged — but that silent default is what made this unsafe, so the intent is stated rather than inherited. Documents the process, what differs from a stable release, how it interacts with the other packages in the monorepo (fixed mode versions only what changed; `next` covers every package published in the run), and that prereleases are cut from main so they are not the tool for validating an unmerged branch.