Repository navigation
fix: verify the Git merge parent before publishing v0.3.0 - #16
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
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.
Direct GitHub API responses in Actions omit
merge_commit_shaeven on full PR details. Publication therefore stopped before writing a tag or release.Bind the release to the actual Git commit object instead: the current main commit must have exactly two parents, and its second parent must equal the reviewed head of the unique merged release PR. Retarget the one-version publisher to
release/v0.3.0-final.Existing repository/branch identity, merged-state, latest main CI/CodeQL, PR dependency review, no-tag-move, and no-release-overwrite requirements remain in place. No new permissions or billing-code changes.
Validation: all eight offline guard tests pass with PR responses that omit merge_commit_sha; wrong-parent and non-merge cases are rejected. Direct read-only API checks confirmed the PR, Git parent relation, workflow runs and absent release/tag; the local network rehearsal was interrupted at its final repeated main read before any write. Required CI and the gated publisher will provide final verification.
Final head
9a5de4cc6d52aea289992441c3c0e7d7d7b4bc5bpassed PR verification, branch verification, CodeQL, and Dependency Review.