ci(ENG-4207): publish an existing release tag to npm on demand
Merged
HI
1d ago+44+44+01234567890123456789-0-0-0123456789
What
Adds a manual workflow_dispatch trigger to release-please.yml that publishes an existing release tag to npm.
Why: when the publish step fails after release-please has cut the release, re-running the job doesn't help. release-please sees the release already exists, reports nothing released, and skips every publish step. That's what happened to defender-v0.9.6.
How: run the workflow from the Actions tab with a tag, e.g. defender-v0.9.6. The new publish-tag job:
- checks the input is a release tag (
defender-vX.Y.Z); - checks out that tag with LFS (for the models);
- checks
package.json's version matches the tag; - builds and publishes with the same steps and
NPM_TOKENas the release job.
On a push to main, only the release-please job runs, as before.
š¤ Generated with Claude Code
Summary by cubic
Adds a manual workflow trigger to release-please.yml to publish an existing release tag to npm when the publish step fails after release-please has already cut the release.
- Re-running the job doesn't help because release-please sees the release already exists and skips publishing.
- The new
publish-tagjob checks the tag format, checks out the tag with LFS, verifiespackage.jsonmatches the tag, then builds and publishes using the same steps andNPM_TOKENas the release job. - On push to
main, only the release-please job runs, keeping the existing behavior.