The pinned Trivy browser-download URL now consistently returns HTTP504 from both the runner host and its job container. GitHub Release Assets API successfully returns the identical archive with the pinned SHA256. Add a fixed API fallback for that exact asset; preserve scanner version/hash, database freshness and all image gates. Both routes failing or a bad hash still stop before extraction or execution.
Validation:98 focused tests passed; independent quick review found no issues. Independent real-container download through API matched the exact pinned checksum. No product changes, asset replacement, tag movement or production deployment. Native CI is run sequentially while CT108 capacity is being resolved.
The pinned Trivy browser-download URL now consistently returns HTTP504 from both the runner host and its job container. GitHub Release Assets API successfully returns the identical archive with the pinned SHA256. Add a fixed API fallback for that exact asset; preserve scanner version/hash, database freshness and all image gates. Both routes failing or a bad hash still stop before extraction or execution.
Validation:98 focused tests passed; independent quick review found no issues. Independent real-container download through API matched the exact pinned checksum. No product changes, asset replacement, tag movement or production deployment. Native CI is run sequentially while CT108 capacity is being resolved.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The pinned Trivy browser-download URL now consistently returns HTTP504 from both the runner host and its job container. GitHub Release Assets API successfully returns the identical archive with the pinned SHA256. Add a fixed API fallback for that exact asset; preserve scanner version/hash, database freshness and all image gates. Both routes failing or a bad hash still stop before extraction or execution.
Validation:98 focused tests passed; independent quick review found no issues. Independent real-container download through API matched the exact pinned checksum. No product changes, asset replacement, tag movement or production deployment. Native CI is run sequentially while CT108 capacity is being resolved.