Repository navigation
docs: record how to tag a release from a proxied agent session - #53
Merged
Merged
Conversation
A remote agent session pushes git through a ref-scoped credential broker. Branch pushes succeed and `refs/tags/*` is refused with HTTP 403 at receive-pack, which reads as an egress denial: `git push --dry-run` passes for the tag the broker then refuses, and the session proxy logs no failure. That combination stopped a release one step from done. Record the remedy where the failure happens, at the end of the publish flow: create the annotated tag on the direct channel through `gh api .../git/tags` and `.../git/refs`, which starts the release workflow exactly as pushing the tag would. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DHVv9huTFEzuF8j8N72F4y
 |
|
Overall Grade |
Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| Secrets |  |
Aug 22, 2026 8:54p.m. | Review ↗ |
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
Coverage Report
File CoverageNo changed files found. |
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
2 participants
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.
Records how to tag a release when
git pushcannot create the tag, which stopped thev0.2.1 release one step from done.
What happens
A remote agent session pushes git through a ref-scoped credential broker. Pushes to
refs/heads/*succeed; pushes torefs/tags/*are refused with HTTP 403 atreceive-pack. Two things make it read as an organization egress denial rather than a
channel limit:
git push --dry-runpasses for the tag the broker then refuses, because dry-runstops at ref advertisement.
nor contradict the theory.
The remedy already exists in
tbd shortcut setup-github-cliunder "Proxied RemoteSessions". This puts it in the runbook, at the step where the failure occurs, so it is
found by someone following the runbook rather than only by someone who thinks to go
looking for it.
The change
One new subsection at the end of Publish the Release, after the normal tag-push flow
and its workflow description, so the primary path still reads straight through. It
records that the 403 is not an egress denial, that a GitHub-host 403 with no
x-github-request-idheader came from the mediation layer, and the twogh apicallsthat create the annotated tag on the direct channel — equivalent to
git tag -a, andstarting the release workflow exactly as pushing the tag would.
Verified in this session: v0.2.1 published to npm with provenance via exactly these
calls after the tag push 403'd.
Related
Filed jlevy/tbd#255 proposing the upstream fix, so every tbd repo gets this at
bootstrap rather than each runbook carrying it.
ensure-gh-cli.shalready detects theproxied-session condition and proves the direct channel works before printing the
NO_PROXYrecipe; it points at the shortcut for the consequence instead of stating it.That is the one place the fact is provably relevant and lands in an agent's context
before it can form a wrong model.
Validation
pnpm ci:qualityclean:format:check,docs:check(138 Markdown files, 18maintained),
lint:check. Docs-only change.🤖 Generated with Claude Code
https://claude.ai/code/session_01DHVv9huTFEzuF8j8N72F4y