Skip to content

fix: Return newest blob when multiple match in metadata version lookup #317

fix: Return newest blob when multiple match in metadata version lookup

fix: Return newest blob when multiple match in metadata version lookup #317

Triggered via pull request January 15, 2026 01:48
Status Failure
Total duration 4m 34s
Artifacts

code_changes.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Test
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.