Repository navigation
ci: fix verify-HEAD routing test on signed checkouts; skip npm republish of existing versions - #379
Merged
Merged
Conversation
…s already-published versions Auths-Id: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Device: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Anchor-Seq: 1
Auths Commit Verification
Result: ✅ 1/1 commits verified |
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
1 participant
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.
Two CI fixes:
test_unified_verify_routes_head_to_commit_verifyassertedauths verify HEADalways fails — true only on unsigned checkouts. Now that main is fully signed and root-pinned, verification legitimately succeeds in CI and the assertion broke. The test now pins what it always meant to: routing. Either verdict must exit 0 or 1 — never clap's usage-error exit 2.publish-node.ymlre-fires on a re-pushed tag and npm refuses republishing an existing version ("You cannot publish over the previously published versions: 0.1.6"). An already-published version is now a stated SKIP, not a red job — re-tagging a release stays green.🤖 Generated with Claude Code