Skip to content

Latest commit

 

History

History
39 lines (22 loc) · 1.51 KB

RELEASE.md

File metadata and controls

39 lines (22 loc) · 1.51 KB

Follow these steps to ensure a smooth and consistent release process.

Release

We currently use changesets for tracking changes, generating changelogs, and publishing releases.

We don't use changesets prerelease mode yet as we want to avoid additonal steps when creating a new release.

1. Update Main with changes from next

  • Make a PR from next into main branch

  • Merge PR into main using a merge commit

2. Publish new package version

  • Changeset bot should now pickup the changesets (inside .changeset/) and generate a PR with bumped version and changelog.

  • Approve and merge the PR.

  • Changeset bot will now publish new a package version to npmjs and create github releases

  • Verify that new version is available in npmjs (under latest tag) and on github releases

3. Deploy new application version to production

  • Manually trigger the github action deployment to production environment from main branch:
    • Deploy Storefront
    • Deploy Theme
    • Deploy Storybook

4. Update next branch with changes from main

  • Make a PR from main into next branch

  • Merge PR into next using a merge commit

Next

  • Use Release Snapshot to publish new version for testing on @next before releasing to production