Make failed publishing in a monorepo less painful #579
Description
Hi,
with the recent changes on npm around trusted publishing, we're regularly running into issues that aren't obvious to fix when managing releases with this action.
The problem boils down to the fact that we add new provider plugins quite regularly to our monorepo but trusted publishing for npm packages can only be configured for already existing packages, so the normal publishing workflow in CI will fail.
The current state of this action will publish all packages that it can to npm. When it encounters one that cannot be published (in our case it would be the first publication of a new plugin) the action errors out. This means that we don't get any git tags and/or releases for any of the already published packages.
I would love to see one of two things:
a) create git tags and releases for all packages that were successfully published to npm as part of the run
b) determine ahead of time whether publishing would succeed for all packages and error out early before publishing anything to npm in case any of the packages would fail
As I think option b) has a lot more corner cases to cover, I'd personally welcome option a) very much.