Browse 0.10.0 uploaded successfully in [the Release
workflow](https://github.com/browserbase/stagehand/actions/runs/35798682312/job/106985029323),
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.
<!-- This is an auto-generated description by cubic. -->
---
## 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.
<sup>Written for commit 345a953e7df218fe103415d4ac62b3c33d218073.
Summary will update on new commits.</sup>
<a
href="https://cubic.dev/pr/browserbase/stagehand/pull/3015?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>
<!-- End of auto-generated description by cubic. -->
