Skip to content

chore(deps): update quay.io/keycloak/keycloak docker tag to v26.7.3 - #1410

Open
renovate-bot-cbcoutinho[bot] wants to merge 1 commit into
masterfrom
renovate/quay.io-keycloak-keycloak-26.x
Open

chore(deps): update quay.io/keycloak/keycloak docker tag to v26.7.3#1410
renovate-bot-cbcoutinho[bot] wants to merge 1 commit into
masterfrom
renovate/quay.io-keycloak-keycloak-26.x

Conversation

@renovate-bot-cbcoutinho

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
quay.io/keycloak/keycloak patch 26.7.226.7.3

Configuration

📅 Schedule: (in timezone Europe/Amsterdam)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@claude

claude Bot commented Aug 31, 2026

Copy link
Copy Markdown

Claude finished @renovate-bot-cbcoutinho[bot]'s task in 21s —— View job


Review: PR #1410 — bump quay.io/keycloak/keycloak 26.7.2 → 26.7.3

  • Gather context (Renovate bump: quay.io/keycloak/keycloak 26.7.226.7.3)
  • Inspect diff
  • Post review feedback

Diff (docker-compose.yml, 1 line changed):

-    image: quay.io/keycloak/keycloak:26.7.2@sha256:9d1f1b2b7261ff53c66cb1092dfcdc34a5fb77e81f9e6a6e75b8b6a795de8067
+    image: quay.io/keycloak/keycloak:26.7.3@sha256:ff4257d0d64efbe99ed1ddfaf07765cc3c36dc7518bf8324d41961327f441c54

Assessment: LGTM. This is a routine Renovate patch bump of the keycloak test-stack image used only by the mcp-keycloak OAuth/OIDC test lane (docker-compose.yml lines ~326+). Notes:

  • Both the tag and the digest were updated together, so the pin stays reproducible/tamper-resistant — no partial-update risk.
  • Patch release within the same minor (26.7.x), so no breaking-change surface expected per Keycloak's own versioning.
  • No application code, MCP tool, or API surface is touched, so the repo's "end-to-end + contract coverage" and "BaseResponse" review gates in CLAUDE.md don't apply here.
  • Per CLAUDE.md's Keycloak testing docs, this only affects the mcp-keycloak container (port 8002) and Keycloak OAuth test lane (uv run pytest -m oauth -v / docker compose up -d keycloak app mcp-keycloak). Since CI will exercise this lane, that's sufficient validation — no manual action needed beyond normal CI checks passing.

No issues found. Safe to merge once CI is green.

@sonarqubecloud

Copy link
Copy Markdown

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