Tags: everettmorgan/retry
Tags
Make publish workflow idempotent and fix legacy dist-tag name npm rejects dist-tags that parse as a semver range, so 1.x releases now publish under "legacy" instead of "v1". The workflow also skips publishing when the version already exists on the registry, so re-running a release (or cutting one after a manual publish) stays green instead of failing on a duplicate version. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>