fix(ci): push Browse tags despite npm propagation delay

Merged
SH
2mo ago
+7-3

Browse 0.10.0 uploaded successfully in the Release workflow, but the following tag step saw a temporary npm 404 and returned unpublished. The job finished green without pushing the release tag.

Push the validated local tag that Changesets creates after a successful upload without requiring immediate registry visibility. When no local tag exists, retain the registry check and original version-bump commit guard for recovery.

Validation: reproduced the failure with a real HTTP server returning 404 and a bare Git remote, then verified the fix; all 67 release tests, tooling typecheck, targeted lint/format, and diff checks pass. The diff changes only the helper and its existing regression test.

The current browse@0.10.0 tag has been repaired separately to the exact commit verified in npm provenance. No npm upload or package version change is part of this PR.


Summary by cubic

Fixes the release workflow so an existing local Browse tag is pushed without waiting for npm registry reads to converge. Previously a temporary 404 from npm during propagation made the tag step return unpublished, finishing green without creating the release tag. When no local tag exists, the registry check and the version-bump-commit guard still run as before.