Repository navigation
ci: normalize release repository API root - #5
Merged
Merged
Conversation
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 v2.15.1 receiver failed before package verification because the shared API helper requested
repos/HitKeep/hitkeep/. GitHub returns 404 for that trailing-slash repository root. Normalize the endpoint once in the helper.Validation: the new regression fails before the fix; all 43 package and release-delivery tests pass afterward. Native GitHub metadata requests reproduce the 404 with the slash and succeed without it. No receiver authorization, artifact validation, or write policy changes.