Commit Graph

4 Commits

Author SHA1 Message Date
Neil e2886ef3fe
chore(release): expose patch/minor/major as Cut Release kinds (#999)
Replaces the `stable` + optional `version` inputs with explicit
`rc | patch | minor | major` choices. Stable kinds are always computed
off the latest published stable release (ignoring intermediate RCs), so
there's nothing to type and no way to pick a version that regresses
electron-updater.

The stable-must-strictly-increase guard stays in place for patch/minor/
major. RC behavior is unchanged — continues an active series or starts
a new one on the next patch.
2026-04-23 11:11:46 -07:00
Neil c4a6701d9f
chore(release): move release cutting to a Cut Release workflow (#972)
Replaces the local `pnpm release:{rc,patch,minor,major}` scripts with a
single manually-dispatched GitHub Actions workflow (`release-cut.yml`)
that takes `kind` (rc|stable), an optional `ref`, and an optional explicit
`version`.

Why: cutting releases locally was too easy to get wrong — `npm version
prerelease` behaves differently depending on whether the current version
is already an rc, there was no guard against tagging a dirty tree or an
off-main branch, and the "bad commit just landed, release the previous
one" case had no first-class answer. The new workflow:

- Resolves the next version automatically from GitHub Releases (or takes
  an explicit override).
- Refuses to cut a stable release whose version isn't strictly greater
  than the latest published stable. This is the only invariant
  electron-updater needs within the `latest` channel.
- Only fast-forwards `main` with the version-bump commit when the caller
  released the tip of `main`. Off-main releases publish only the tag, so
  main is never polluted by a one-off RC against a feature branch.

CONTRIBUTING.md now documents the new flow with the common scenarios
(normal release, bad-commit-revert-to-previous-SHA, one-off RC, explicit
minor/major). The scheduled RC cron in release-rc.yml is untouched.
2026-04-22 23:20:04 -07:00
Jinjing aedd4f7b4f
docs: update README for CLI integration and improve conversion (#279)
This commit completely overhauls the README to prominently feature the new Orca CLI orchestration capabilities. It also revamps the page structure for better conversion by adding trust badges, explicit cross-platform support text, a 'Quick Start' guide, and a dedicated 'Why Orca?' section. Lastly, the CONTRIBUTING.md guide was updated to encourage contributors to provide their Twitter handle for shoutouts.
2026-04-03 20:56:34 -07:00
Jinjing ecec55aca4
docs: add contribution guide and PR template (#163) 2026-03-28 10:44:02 -07:00