fix(ci): point keycloak image at new working namespace (unblock integration tests) - #1844
Merged
Conversation
The previously used image ghcr.io/hyperledger/identus-keycloak-plugins:0.2.0 is broken on GHCR — orphaned under the legacy `hyperledger` org, its platform manifests were garbage-collected and `docker pull` fails with "manifest unknown". This has been blocking every integration-test run (keycloak container fails to start) since mid-July. The image has been republished under the repo-linked namespace ghcr.io/hyperledger-identus/keycloak-plugins (auto-linked to the hyperledger-identus/keycloak-plugins repo, so it can no longer be orphaned/GC'd), and version 0.2.1 has been released there. Update the integration-test compose file and the OID4VCI examples to the new namespace + 0.2.1. Signed-off-by: Pat Losoponkul <patextreme@hotmail.com>
|
Contributor
Integration Test Results (prism-node)1 tests 1 ✅ 1s ⏱️ Results for commit 764f9f2. |
Contributor
Integration Test Results 23 files 23 suites 3s ⏱️ Results for commit 764f9f2. |
Contributor
patextreme
added a commit
that referenced
this pull request
Jul 28, 2026
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>
patextreme
added a commit
that referenced
this pull request
Jul 28, 2026
…1844) 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.
Problem
Integration tests have been failing at startup on every PR since mid-July:
```
tc.docker - keycloak Pulling
tc.docker - manifest unknown
IntegrationTestsRunner > classMethod FAILED
```
The referenced image `ghcr.io/hyperledger/identus-keycloak-plugins:0.2.0` is broken on GHCR — orphaned under the legacy `hyperledger` org, its platform manifests were garbage-collected, so `docker pull` returns `manifest unknown`.
Fix
The image has been republished under the repo-linked namespace `ghcr.io/hyperledger-identus/keycloak-plugins` (auto-linked to the keycloak-plugins repo, so it can't be orphaned/GC'd again), and 0.2.1 is published there. Verified anonymously:
```
$ docker pull ghcr.io/hyperledger-identus/keycloak-plugins:0.2.1
Status: Downloaded newer image ... # index 200, arm64+amd64 manifests OK
```
This PR repoints the three references to the new namespace + `0.2.1`:
Related
Note: the keycloak-plugins `release.yml` failed at its final step (pushing the release commit/tag to the signature-protected `main`) — but the image was already pushed before that, so `0.2.1` is available. The release-bookkeeping issue is tracked separately and doesn't affect this image.