FDC3
FDC3 copied to clipboard
GitHub Release Action
Minor Issue
- Releases to NPM should be done from a release tag, rather than main or release branches.
- Releases should be kicked off by a GitHub release being created
- The release workflow should include the coverage workflow as a precondition to check everything is correct.
FDC3 .net shows how this can be done.
Edited - the release to NPM should happen from the release tag itself (so the SHA of the release points to exactly whats in the corresponding NPM packages) rather than main.
Note:
- #1528
could be dealt with at the same time as this in the revised workflow