Skip to content

Bump keycloak theme to v2.1.0#2819

Merged
joshestein merged 1 commit into
masterfrom
josh/bump-keycloak-version
Jul 23, 2026
Merged

Bump keycloak theme to v2.1.0#2819
joshestein merged 1 commit into
masterfrom
josh/bump-keycloak-version

Conversation

@joshestein

Copy link
Copy Markdown
Collaborator

Description

Bumps keycloak theme to v2.1.0

Notable changes:

  1. Google sign in moved above email sign in
  2. First/last name (optional) fields added to sign up form

Issue

Fixes #2723

@Will-Howard
Will-Howard temporarily deployed to josh/bump-keycloak-version - bluedot-preview PR #2819 July 23, 2026 10:26 — with Render Destroyed
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ae51218e-8a6c-4b7b-aea8-58fe3df228d9

📥 Commits

Reviewing files that changed from the base of the PR and between 5bb67fa and 224d62a.

📒 Files selected for processing (1)
  • apps/login/tools/getBluedotKeycloakTheme.sh

📝 Walkthrough

Walkthrough

Updated the Keycloak theme download script to use the v2.1.0 GitHub release instead of v2.0.0. Added a console message confirming the downloaded asset name and release version.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch josh/bump-keycloak-version

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Will-Howard
Will-Howard temporarily deployed to josh/bump-keycloak-version - bluedot-storybook-preview PR #2819 July 23, 2026 10:26 — with Render Destroyed
@joshestein joshestein changed the title Bump keycloak version Bump keycloak theme to v2.1.0 Jul 23, 2026
@joshestein
joshestein marked this pull request as ready for review July 23, 2026 10:32
@joshestein
joshestein merged commit b2d185f into master Jul 23, 2026
8 checks passed
@joshestein
joshestein deleted the josh/bump-keycloak-version branch July 23, 2026 10:32
@greptile-apps

greptile-apps Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR updates the Keycloak login theme release.

  • Pins the downloaded theme to v2.1.0.
  • Adds the missing trailing newline to the download script.

Confidence Score: 4/5

The changed artifact download path needs HTTP failure validation before merging.

  • The new pin is used by the login build and deployment path.
  • An HTTP error body can be saved as the provider JAR and fail later in the Keycloak image build or startup.

apps/login/tools/getBluedotKeycloakTheme.sh

Important Files Changed

Filename Overview
apps/login/tools/getBluedotKeycloakTheme.sh Updates the theme release pin to v2.1.0; an unavailable or mismatched asset can pass the download step as an invalid JAR.

Reviews (1): Last reviewed commit: "Bump keycloak version" | Re-trigger Greptile

cd $(dirname "${BASH_SOURCE[0]:-$0}")/..

FIXED_RELEASE_VERSION="v2.0.0"
FIXED_RELEASE_VERSION="v2.1.0"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P1 Invalid Release Asset Passes Download

This new pin changes the artifact URL used by every login build, but the downloader accepts HTTP error responses because its curl call lacks --fail. If the v2.1.0 asset is temporarily unavailable or has a different filename, the response body is saved as the provider JAR and reaches the Keycloak image build, which can fail during build or startup instead of stopping at the download.

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.

Require user's full name during sign up flow

2 participants