Page Comparison

10 minutes

The future of publishing from master

Brian Smith

• Do we want to keep publishing to npm from the master branch?

  • Take advantage of prerelease to publish as it merges before publishing to npm on main branch

  • Even on named release branches (22/23 etc.) per commit may be too granular

• Temp plan:

  • Make 22 and 23 branches

  • Make 23 branch default on repo

  • Update netlify to publish from 23

  • Rename master to next to make it clear that’s where breaking changes should land

    • Figure out prerelease publishing from next

• Sidenote (but important): better communication of what breaking changes are in a breaking change release

• When communicating out ping djoy to see if this aligns well with his plans for frontend-base

• Communicate with UI/UX WG about breaking changes that impact design/accessibility before release