Repository navigation
test(web): have the other machine's hmz say this version, not 0.0.0 - #389
Merged
Merged
Conversation
A release branch's hmz is not 0.0.0, so the stand-in host was found at another version and replaced, failing the web topic on every release pull request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release PR for 0.2.0-beta.1 (#386) failed the
webintegration topic: the stand-in ssh host'shmzsaid0.0.0while the release branch's is0.2.0b1, soRemotesreinstalled it. The stand-in now says this package's version by default, and the state assertion expects it.Checked locally with
versionset to both0.0.0and0.2.0b1.🤖 Generated with Claude Code