Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release/v4, this PR will be updated.

Releases

modular-scripts@3.0.0

Major Changes

• #1421
  e5d772f
  Thanks @cristiano-belloni! - Upgrade
  to Webpack 5

Patch Changes

• #1478
  bec55a5
  Thanks @dependabot! - Bump rollup from
  2.67.2 to 2.70.1

• #1492
  810934b
  Thanks @dependabot! - Bump commander
  from 8.2.0 to 9.1.0

• #1510
  4846d21
  Thanks @cheemcheem! - Fix bug that prevented
  lint diff from running

create-modular-react-app@2.1.5

Patch Changes

• #1492
  810934b
  Thanks @dependabot! - Bump commander
  from 8.2.0 to 9.1.0

[LukeSheard]

@cristiano-belloni something is wrong with the release branches as this is triggering a normal release of modular. Looks like there should be a check that release/** branches are in pre-release mode, the opposite to main release flow.

[cristiano-belloni]

@cristiano-belloni something is wrong with the release branches as this is triggering a normal release of modular. Looks like there should be a check that release/** branches are in pre-release mode, the opposite to main release flow.

Even if you open a pre-release in this branch now, you will get the wrong version, no matter if you branch off main or release-webpack-5 (in both cases I think you'll get a 3.0 based alpha, which is wrong). I should probably have parked this in a feature/ branch and kept it in sync with main till after the release of 3.0, at which point I could have created the release branch.
Anyway, we don't normally want to have two pre-releases around at the same time - this is a special occasion due to two breaking changes being queued to be released (and tested) one after the other. We can ignore this changeset until it's time to use it.