github: pin gateway v0.6.0 (Opus 5, /gateway check) - #1188
Merged
Conversation
Bumps both pins together: the gateway-action SHA and the runtime_ref it resolves. runtime_ref is pinned explicitly rather than left to the action's default, so bumping only the action would leave the job on the v0.5.0 runtime. v0.6.0 adds no trigger and no input, so the rest of the shim is unchanged. Also corrects a copy-paste artifact in the adjacent comment, which said runtime upgrades go through an lnd PR.
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
hieblmi
self-requested a review
July 28, 2026 07:07
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.
Pin the gateway shim to v0.6.0.
Both pins move together
uses: lightninglabs/gateway-action@3a31b86(v0.5.0)334a845(v0.6.0)runtime_ref:b7490e6(gateway v0.5.0)75f6e67(gateway v0.6.0)runtime_refis pinned explicitly rather than left to the action's default, so a runtime upgrade goes through a PR here instead of a moved tag. Bumping only the action SHA would leave the job running the v0.5.0 runtime while the comment claimed v0.6.0.v0.6.0 adds no trigger and no input, so the rest of the shim is unchanged — no new permissions, no new secrets, no new events.
Drive-by fix
The comment above
runtime_refsaid runtime upgrades "go through an lnd PR" — a copy-paste artifact from the lnd shim. Now says loop.What v0.6.0 brings
/gateway check— an advisory "have my fixes landed?" report. Evaluates the open findings on a PR against the current diff and reports one line each (addressed,partially addressed,unresolved,unclear) with a pointer to the evidence. Bare/gateway checksweeps everything;/gateway check F2 F5narrows it. Open to PR authors as well as maintainers, and it writes nothing —/gateway re-reviewremains the only thing that moves a finding's recorded status.path:line, so a finding copied out of GitHub keeps its location/gateway dismissand/gateway promoteno longer delete the finding's comment thread — they annotate in place and resolve it, so replies and any/gateway explainoutput survive