One-click GitHub Release workflow added for maintainers
Maintainers can now publish GitHub Releases from the Actions tab without touching the command line — the workflow validates versions, gates on tests, bumps all workspace package.json files, and creates a release with auto-generated notes.
Publishing a release used to mean running a sequence of manual commands: bumping versions, tagging, pushing, creating the release, and hoping nothing broke along the way. For monorepos with multiple workspaces, the process invited typos and inconsistencies.
A new GitHub Actions workflow lets maintainers publish a release in one click from the Actions tab. They enter a semver version — say 1.0.0 or 1.1.0-rc.1 — and the workflow takes over. It validates the version string and checks that the tag does not already exist, then gates on yarn typecheck and yarn test before touching anything. All three package.json files in the monorepo are bumped in lockstep, committed, and pushed to main. The immutable version tag and a moving major-pointer tag are created together, and the GitHub Release is generated with auto-generated release notes. Pre-release versions (those with a hyphen suffix) are flagged automatically.
The change is scoped to project infrastructure — it touches only the CI pipeline and documentation — but it removes the last manual step in the release process.