Make the release probe use authenticated Git transport - #94
Merged
Merged
Conversation
srinji-kaggss
force-pushed
the
fix/release-probe-git-transport
branch
from
August 30, 2026 18:15
2f6825e to
4ca3f08
Compare
6 tasks
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.
The release probe now works against Braid's actual GitHub URL under the repository's authenticated Git configuration.
Gap
PR #93 proved the locked consumer with a local Git URL, but the first post-merge public-URL probe failed before dependency resolution. Cargo's embedded Git client observed the local HTTPS-to-SSH rewrite and could not use the existing Git authentication. A green local-file probe was therefore not sufficient release evidence.
Fix
scripts/braid-release-probe.shnow defaults Cargo to the Git CLI transport while still honoring an explicit caller override. Git is already intrinsic to a Git-sourced contract; this adds no library dependency and lets Cargo use the same credential and URL configuration as the operator's working Git client.The CI scope classifier now treats shell scripts and workflow YAML as code. A release-gate change can no longer take the docs-only path and skip its own verification lane.
Rejected alternative: document a one-off environment variable. That would leave the canonical release command broken on the machine that must run it and make success depend on remembered shell state.
Regression proof
https://github.com/srinji-kaggss/Braid.gitatdf45d01413b658a6afea6fb0c0e4bbb8661d932a: locked consumer compiled; registry CID and capsule CID matched; verdict admit.4ca3f086962a3bbd6a974b07bc108c316f0c2ecb.Advances #75.
Still not done: this fix must pass GitHub CI and merge before tag promotion. No tag or crates.io release is created here.