You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release process is manual, hence it is difficult to release early, release often.
This repo will become a multi-repo soon #802 and hence we need to make the releasing of the various packages easier.
Ideally, one button click should be enough for a maintainer to release and publish.
Also, automation of the changelog should be considered, using Conventional Commits
Acceptance Criteria
Changelog is maintained from commits using conventional commits
New PR automatically opens when changes are merged, version (patch, minor) is deduced from conventional commits (breaking change or not)
Maintainer can merge PR for release to happen
Minimum manual action should still be needed from the maintainer
Automated release and publication of all merged PR under a release candidate version (ie 0.23.0-<short commit hash>) with a next tag on npmjs.com Auto-release merged PRs #896
This is a change request
Problem
The release process is manual, hence it is difficult to release early, release often.
This repo will become a multi-repo soon #802 and hence we need to make the releasing of the various packages easier.
Ideally, one button click should be enough for a maintainer to release and publish.
Also, automation of the changelog should be considered, using Conventional Commits
Acceptance Criteria
0.23.0-<short commit hash>
) with anext
tag on npmjs.com Auto-release merged PRs #896Notes
Check out the following repos for ideas:
The text was updated successfully, but these errors were encountered: