Repository navigation
Conversation
Ekhorn
added this pull request to stack #41
October 2, 2026 13:24
The pages here replace Keycloak's own, so the message keys they name and the set of pages that exist are upstream's, and an upgrade can move either while everything still compiles. scripts/check-keycloak-drift.mjs fails on: - a page in src/pages that the Keycloak the Dockerfile pins no longer has - a message key the theme names that Keycloak no longer defines - a stand-in in i18n.ts that Keycloakify has caught up with and now ships On a branch that moves the pinned version it also reports which of Keycloak's own versions of our pages changed between the two. It keeps no baseline: a version's templates never change, so the published jar for each version is the record.
Ekhorn
force-pushed
the
28-migrate-kc-themes-to-vaadin-part-2
branch
from
October 2, 2026 14:01
655ef8c to
b10b6f0
Compare
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 pages here replace Keycloak's own, so the message keys they name and the set
of pages that exist are upstream's, and an upgrade can move either while
everything still compiles.
scripts/check-keycloak-drift.mjs fails on:
On a branch that moves the pinned version it also reports which of Keycloak's own
versions of our pages changed between the two. It keeps no baseline: a version's
templates never change, so the published jar for each version is the record.
Stack created with GitHub Stacks CLI • Give Feedback 💬