workflow: separate version bumping and publishing on release

[antfu]

Workflow Changes

• npm run release script moved to top-level with an interactive prompt to select the package
• version bumping is done with npm run release instead of GH action dispatching
• The flow of releasing becomes:
  1. Maintainer runs npm run release locally at project root of the latest main branch
  2. Select the package and version that need to be released
  3. The scripts handle version bumping, changelog, git commit with tag and push it to GH
  4. The commit tag triggers Actions to do the building and publishing on CI https://github.com/vitejs/vite/actions/workflows/publish.yml
  5. Done.

Changes Details

• npm run release moved to root, and no longer runs building and publishing.
• --skipBuild option has been removed. We use prepublishOnly hook to trigger the build before publishing.
• changelog scripts in each package has been inlined in the release script to reduce duplication
• Use npm publish instead of yarn publish since we already handle the version bumping.

New Features

• npm run release will show commits between the last release of a package for the maintainer to reference

[antfu]

TODO: remove the --dry flag

[patak-dev]

The flow looks awesome Anthony, after seeing the three clicks (because of the environment approval) and waiting at each step for the GitHub UI to respond when using dispatch, it makes a lot more sense to use the CLI as you proposed.

[antfu]

Kapture.2022-02-12.at.18.39.48.mp4

Added a little helper to show the git diff since the last release