Publishing pipeline is a long one and can have multiple points of failure. I usually publish a preview package to check everything works fine before doing a release. The issue comes when publishing fail (because of bad version tagging, naming,...). You end up with different preview packages, not uniformly uploaded. It can be solved by using a dry run of npm publish. if a dry run works, then publishing a preview is less needed and if it fails, there are no more 'zombie' packages.
This can be done in the publish preview with a checkbox in the github action parameter window. if dry run, then add the corresponding parameter to the publish action.
CedricGuillemet
commented
1 year ago
Publishing pipeline is a long one and can have multiple points of failure. I usually publish a preview package to check everything works fine before doing a release. The issue comes when publishing fail (because of bad version tagging, naming,...). You end up with different preview packages, not uniformly uploaded. It can be solved by using a dry run of npm publish. if a dry run works, then publishing a preview is less needed and if it fails, there are no more 'zombie' packages. This can be done in the publish preview with a checkbox in the github action parameter window. if dry run, then add the corresponding parameter to the publish action.