Conversation
Marin2409
force-pushed
the
tool-private-registry-sdk-migration
branch
2 times, most recently
from
September 28, 2026 19:10
846c96e to
964df9a
Compare
Marin2409
marked this pull request as ready for review
September 28, 2026 20:22
Marin2409
force-pushed
the
tool-private-registry-sdk-migration
branch
6 times, most recently
from
October 2, 2026 16:09
4d4b508 to
dd47069
Compare
Marin2409
force-pushed
the
tool-private-registry-sdk-migration
branch
from
October 2, 2026 16:43
7f413a5 to
8d77be6
Compare
This branch has not been deployed
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.
This PR continues the work from PR #514 and takes over the Private Registry tools migration.
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.