fix(examples): bump keycloak-plugins Nickel stack version to 0.2.1 - #1845
Merged
Conversation
The new ghcr.io/hyperledger-identus/keycloak-plugins namespace only has the 0.2.1 tag published; 0.2.0 does not exist there (HTTP 404). #1844 migrated the namespace in stack.ncl but left versions.ncl pinned to 0.2.0, so the external-keycloak Nickel stack resolved to a non-existent image. Signed-off-by: Pat Losoponkul <patextreme@hotmail.com>
|
Contributor
Contributor
Contributor
patextreme
added a commit
that referenced
this pull request
Jul 28, 2026
…1845) Signed-off-by: Pat Losoponkul <patextreme@hotmail.com>
This was referenced Jul 28, 2026
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.
Summary
Follow-up to #1844 (just merged), which migrated the keycloak-plugins image to the repo-linked namespace
ghcr.io/hyperledger-identus/keycloak-plugins.#1844 missed
examples/.nickel/versions.ncl, which still pinsidentusKeycloak = "0.2.0". The Nickel external-keycloak stack (stack.ncl) resolves its image tag from this variable:The new namespace only has
0.2.1published —0.2.0returns HTTP 404 (manifest unknown), the exact failure this migration was fixing. So the example stack would fail to pull.This bumps the variable
0.2.0 → 0.2.1.Verification
Why this wasn't caught by CI
The integration tests use
tests/.../keycloak-oid4vci.yml(correctly at0.2.1since #1844), so CI is green. The Nickel stack is a deployment example, not exercised by CI — hence the gap.One-line change, no code impact.
Signed-off-by: Pat Losoponkul patextreme@hotmail.com