Repository navigation
fix(github): Filter artifacts by name when fetching revision artifact - #880
Merged
Merged
Conversation
Listing all artifacts of a repository via the GitHub API is slow and fails with HTTP 500 on repositories with many artifacts, which breaks releases for projects using the legacy artifact lookup where the artifact name equals the revision SHA. Pass the revision as the name filter so GitHub only returns matching artifacts. This avoids the failing unfiltered listing and removes the need to page through unrelated artifacts. Fixes GH-879 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The legacy lookup now requests a single artifact by name, so make the debug, trace, and info messages say which artifact name is being fetched instead of implying all artifacts of the repository are listed. Refs GH-879 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
itaybre
marked this pull request as ready for review
September 25, 2026 17:35
7 tasks
This branch was successfully 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
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.
The legacy GitHub artifact lookup (artifact name equals the revision SHA) listed every artifact in the repository and scanned pages client-side. On repositories with many artifacts, that unfiltered listing is slow and fails with HTTP 500, which breaks releases. The artifact list request now passes the revision as the
namefilter so GitHub only returns the matching artifacts.Server-side name filter
The
GET /repos/{owner}/{repo}/actions/artifactsrequest now includesname=<revision>. Verified against the repository from the issue: the unfiltered request fails, while the filtered request returns the single matching artifact. The existing paging and date-based cutoff are unchanged and act as a fallback if the API ever returns more than one page.Fixes #879
🤖 Generated with Claude Code