chore(release): make pnpm release interactive with version override
Show pending changeset summaries, compute the proposed semver via `pnpm changeset status --output`, and prompt for an override before applying. If the user picks a different version, post-process every fixed-group package's package.json + CHANGELOG.md heading so the commit, npm publish, and tag all use the chosen version. --yes and --dry-run skip the prompt and accept the proposed version. Adds a changeset for the recent SetupWizard scroll + model onboarding handoff fixes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -84,6 +84,9 @@ This will trigger `release.yml` to build binaries and create a GitHub Release. N
|
||||
|--------|-------------|
|
||||
| `pnpm changeset` | Add a new changeset |
|
||||
| `pnpm changeset status` | Check pending changesets |
|
||||
| `pnpm release` | Local interactive release: previews changesets, lets you accept or override the proposed version, then bumps + builds + publishes + tags |
|
||||
| `pnpm release --yes` | Same, but auto-accepts the proposed version and skips the final confirmation |
|
||||
| `pnpm release --dry-run` | Walks through the same preview/version-selection flow without publishing or pushing |
|
||||
| `pnpm release:version` | Apply changesets and bump versions (used by CI) |
|
||||
| `pnpm --filter @runfusion/fusion build:exe` | Build binary for current platform |
|
||||
| `pnpm --filter @runfusion/fusion build:exe -- --target <target>` | Cross-compile for a specific platform |
|
||||
|
||||
Reference in New Issue
Block a user