Our previous release process involved an ADO pipeline which would push to npm and create tags. The new tags would trigger the create_release gh action which would "finish off the release."
Now, however, our create_release GH action is responsible for publishing the package. We could trigger it after a successful automated CI run on main or decide to keep publishing a semi-manual process.
Our previous release process involved an ADO pipeline which would push to npm and create tags. The new tags would trigger the
create_releasegh action which would "finish off the release."Now, however, our
create_releaseGH action is responsible for publishing the package. We could trigger it after a successful automated CI run onmainor decide to keep publishing a semi-manual process.