This modifies release.yml so that publishing to WAPM may fail when the release workflow is triggered manually (i.e. workflow_dispatch).
This lets developers manually retry a release and "skip" (i.e. not error out) on when you get a "wasmer/wasmer-pack v1.2.3 has already been published" error.
You still need to keep an eye on the release job to make sure packages really were published successfully, but at least now there is an escape hatch for dealing with WAPM auth issues (e.g. if the WAPM_PROD_TOKEN secret is no longer accessible).
This modifies
release.yml
so that publishing to WAPM may fail when the release workflow is triggered manually (i.e.workflow_dispatch
).This lets developers manually retry a release and "skip" (i.e. not error out) on when you get a "wasmer/wasmer-pack v1.2.3 has already been published" error.
You still need to keep an eye on the release job to make sure packages really were published successfully, but at least now there is an escape hatch for dealing with WAPM auth issues (e.g. if the
WAPM_PROD_TOKEN
secret is no longer accessible).