Skip to content

fix: follow Registry API Link pagination when listing tags - #84

Closed
Abhinesh Jha (Abhineshhh) wants to merge 1 commit into
microsoft:mainfrom
Abhineshhh:fix/registry-tags-pagination
Closed

fix: follow Registry API Link pagination when listing tags#84
Abhinesh Jha (Abhineshhh) wants to merge 1 commit into
microsoft:mainfrom
Abhineshhh:fix/registry-tags-pagination

Conversation

@Abhineshhh

Copy link
Copy Markdown
Contributor

Description

GetTags performed a single tags/list request and ignored the Link: rel="next" header, so large repositories could silently drop tags before filtering and --max-tags.

Related Issue

Fixes #76

Changes

  • Page with n=100 and follow next links until exhausted
  • Resolve relative Link URLs against the request URL
  • httptest multi-page unit tests

Checklist

  • task lint passes locally
  • task test passes locally
  • Documentation updated (if applicable)

GetTags issued a single tags/list request and ignored the Link
rel=next header, so large repositories could silently drop tags
before filtering and --max-tags selection.

Page with n=100 and follow next links until exhausted; add unit tests
with a multi-page httptest server.

Fixes microsoft#76
@Abhineshhh

Copy link
Copy Markdown
Contributor Author

Closing in favor of a consolidated stack to avoid multi-PR conflicts on the same files.

Superseded by consolidated registry stack (pagination is included there).

Please review the replacement PR linked above (Trivy stack or registry stack).

@Abhineshhh

Copy link
Copy Markdown
Contributor Author

Replacement: #88 (registry stack).

@Abhineshhh
Abhinesh Jha (Abhineshhh) deleted the fix/registry-tags-pagination branch July 16, 2026 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: GetTags does not follow Registry API pagination (Link header)

1 participant