Skip to content

fix: pin this repo's own gatehouse hook to 0.26.0 - #54

Merged
fatherlinux merged 1 commit into
mainfrom
fix/own-gatehouse-pin-0.26.0
Nov 17, 2026
Merged

fatherlinux merged 1 commit into
mainfrom
fix/own-gatehouse-pin-0.26.0

Conversation

@fatherlinux

Copy link
Copy Markdown
Member

The Containerfile bumps moved GATEHOUSE_VERSION to 0.26.0 but never this repo's own pre-commit hook, still on quay.io/crunchtools/gatehouse:0.23.0. That predates GATEHOUSE_LLM_BASE_URL (0.24.0), so the hook ignored the seat's Trentina proxy and sent the proxy token straight to OpenRouter: 401 "key rejected".

  • .pre-commit-config.yaml: gatehouse 0.23.0 -> 0.26.0
  • CHANGELOG.md: [Unreleased] line
  • examples/pre-commit-classic.yaml uses :latest; left as is.

Verified: the gatehouse hook at 0.26.0 ran on this staged diff through the proxy, 18 calls, no 401, "No issues found". shellcheck, host-contract and gourmand passed locally too. The ruff hooks could not run on the seat: the gateway refuses the astral-sh/ruff-pre-commit clone (repo_not_listed), and they don't apply to YAML/Markdown anyway; CI covers them.

🤖 Generated with Claude Code

https://claude.ai/code/session_01R7Y1jckWHhAgXg2WBwkWbb

The Containerfile bumps moved GATEHOUSE_VERSION to 0.26.0 but never the
repo's own pre-commit hook, still on 0.23.0. That predates
GATEHOUSE_LLM_BASE_URL (0.24.0), so the hook ignored the seat's Trentina
proxy and sent the proxy token straight to OpenRouter, which answered 401.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R7Y1jckWHhAgXg2WBwkWbb

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gatehouse found no issues.

Full review.

1 of 8 agents served by google/gemini-3.1-flash-lite (primary unavailable).

@fatherlinux

Copy link
Copy Markdown
Member Author

Approve (second review, a156).

  • Diff at ca9245a is only two files: .pre-commit-config.yaml (+1/-1) and CHANGELOG.md (+4).
  • The hook line differs only in the tag, 0.23.0 → 0.26.0. --env-file "$HOME/.config/mcp-env/gatehouse.env", -v .:/src:ro,z, -w /src, --stdin, --events-backend=none and --log-driver=none are all byte-identical.
  • quay.io/crunchtools/gatehouse:0.26.0 exists: digest sha256:1801c8b9b139b0c42adcf0b851d013481098505a9fe28de78c7f500030fe27f8, pushed 2026-11-17 09:37 UTC. It matches the 0.7.1 Containerfile bump, so the hook and the image now pin the same reviewer.
  • In the head file, the CHANGELOG entry sits under ## [Unreleased] → ### Fixed, after the sdlc ci does not say which push verdicts a repo's [tool.sdlc.push] skip removed #50 entry and before ## [0.7.1]. GitHub reports the merge as clean.

Not in this PR's scope, but the link refs at the bottom of the CHANGELOG are stale. [Unreleased] still compares v0.7.0...HEAD and there is no [0.7.1] ref. The next release PR should fix both.

🤖 Generated with Claude Code

@fatherlinux
fatherlinux merged commit c0736ee into main Nov 17, 2026
10 checks passed
@fatherlinux
fatherlinux deleted the fix/own-gatehouse-pin-0.26.0 branch November 17, 2026 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant