Release Process

The release process for deploying webpack is actually quite painless. Read through the following steps, so you have a clear understanding of how it's done.

Pull Requests

When merging pull requests into the main branch, select the Create Merge Commit option.

Releasing

Releases are automated with changesets:

1. Every user-facing pull request adds a changeset file in .changeset/ declaring its bump level (patch, minor or major).
2. On every push to main, the release workflow updates a chore(release): new release pull request that consumes the pending changesets, bumps the version in package.json and writes CHANGELOG.md.
3. Merging that pull request publishes the new version to npm and creates the matching git tag and GitHub release.

Cutting a release means merging the release pull request. When that happens (patch releases as soon as possible, minor releases every four weeks) is described in RELEASE_SCHEDULE.md.