The following details the process to create a new release. The deployment to GitHub, NPM and YarnPKG are automated and should occur up a Release & Publish to NPM
workflow being successfully finished.
- Update the
CHANGELOG.md
file, located at the root of this corresponding package directory (for example,packages/web-core/CHANGELOG.md
), with the list of changes, fixes and features that are included with the new release. TheCHANGELOG.md
file should be compatible with following format. I.e. it should start fromUnreleased
line. - Create a PR and merge all changes into
main
. - Once this is completed, navigate to the
Actions
page for this repository. - Find
Release & Publish to NPM
workflow. Run it manually. Don't forget to select package and increment: patch, minor or major.
- Update the
CHANGELOG.md
file, located at the root of this corresponding package directory (for example,packages/web-core/CHANGELOG.md
), with the list of changes, fixes and features that are included with the new release. TheCHANGELOG.md
file should be compatible with following format. I.e. it should start fromUnreleased
line. - Create a PR.
- Navigate to the
Actions
page for this repository. - Find
Release & Publish to NPM
workflow. Run it manually. Select your branch from the branches list, selectbeta
increment and type version that you want to publish as beta. For example, if the latest version is1.1.0
and then next one will be1.2.0
, type1.2.0-beta.x
.