Merged
Conversation
…y aligned when attempting to add a federated registry to the primary cluster
xingzhang-suse
changed the title
lsongsuse
approved these changes
Apr 4, 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
2 participants
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.
#1175 The 'fed' prefix and the registry name are not properly aligned when attempting to add a federated registr when attempting to add a federated registry to the primary cluster
Moved the prefix content to lower position
By default, show the field title as floating top style is there is prefix, no matter if there is value in the field
#1177 Upgrade lodash into v4.18.0 + to deal with the CVE-2026-4800