Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cherry-pick] ] support accessory in either order #19906

Merged
merged 4 commits into from
Jan 25, 2024

Commits on Jan 15, 2024

  1. remove the log for ScannerSkipUpdatePullTime

    fixes goharbor#19795, remove the noise in the log
    
    Signed-off-by: wang yan <wangyan@vmware.com>
    wy65701436 committed Jan 15, 2024
    Configuration menu
    Copy the full SHA
    6242b0a View commit details
    Browse the repository at this point in the history

Commits on Jan 24, 2024

  1. support accessor in either order

    In certain cases, the OCI client may push the subject artifact and accessory in either order.
    Therefore, it is necessary to handle situations where the client pushes the accessory ahead of the subject artifact.
    
    Signed-off-by: wang yan <wangyan@vmware.com>
    wy65701436 committed Jan 24, 2024
    Configuration menu
    Copy the full SHA
    3d4946d View commit details
    Browse the repository at this point in the history
  2. fix issue 19392

    Needs to set the repo when to handle the accessory before subject manifest.
    
    Signed-off-by: wang yan <wangyan@vmware.com>
    wy65701436 committed Jan 24, 2024
    Configuration menu
    Copy the full SHA
    13e63e4 View commit details
    Browse the repository at this point in the history
  3. fix the landing accessory data (goharbor#19661)

    Fix the keywords when to list accessories belong to the subject manifest.
    
    Signed-off-by: wang yan <wangyan@vmware.com>
    wy65701436 committed Jan 24, 2024
    Configuration menu
    Copy the full SHA
    170e1e5 View commit details
    Browse the repository at this point in the history