Repository navigation
Conversation
LibGit2.push can return successfully when the server accepts the objects but rejects the reference update. Fetch the remote main branch after pushing and stop before releasing or registering unless it points at the new wrapper commit. Pass that commit to ghr when it creates the release tag. Also turn Pkg registry update errors into exceptions so wrapper versions and registration metadata are never computed from a stale General registry.
giordano
approved these changes
Aug 27, 2026
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.
LibGit2.push does not report reference updates the server refused or failed to apply: the objects are uploaded, the branch stays put, and no error is raised. Registration then built a release and a registry PR on top of the previous wrappers (aws_c_common_jll 1.0.0, 2026-08-26).