Repository navigation
fix(supply-chain): pass DHI pull creds to promote-core; re-pin caller - #31
Conversation
…thub@5825ec5 The dhi-postgres-17 bake run failed in promote-core's scan job with a 401 from dhi.io: the scan job pulls the bytes (mirror-verify only resolves the digest) and had no upstream credentials. .github #237 added optional UPSTREAM_REGISTRY_USERNAME/TOKEN secrets to promote-core; pass the DHI creds through and re-pin both reusable-workflow refs to the SHA that carries the fix. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 12 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Dependency ReviewThe following issues were found:
License Issues.github/workflows/supply-chain-mirror.yml
OpenSSF Scorecard
Scanned Files
|
|
PR ReviewPREMISE: OK — minimal, correctly-scoped forward fix. No Critical or Important findings; safe to merge. Verification (all PR-body claims confirmed):
Suggested (non-blocking):
Note: CodeRabbit's check is green but its review was rate-limited (no substantive review ran); Copilot was not requested. This agent review is the substantive coverage. 🤖 Generated with Claude Code |



Summary
Follow-up to the
dhi-postgres-17bake run, which failed inpromote-core's scan job with401 Unauthorizedfromdhi.io. The scan job pulls the candidate bytes (mirror-verify only resolves the digest) and had no upstream credentials..github #237 (merged) added optional
UPSTREAM_REGISTRY_USERNAME/UPSTREAM_REGISTRY_TOKENsecrets topromote-core. This PR:DHI_REGISTRY_USERNAME/DHI_REGISTRY_TOKENthrough to those secrets.uses:(mirror-verify + promote-core) to.github@5825ec5, the commit carrying the auth fix.Validation
yaml.safe_loadclean;actionlintclean; both SHA pins confirmed updated (old SHA absent); pre-commit passes.After merge
Re-run "Supply Chain Mirror (bake)". The scan job should now authenticate to dhi.io and proceed into Grype/Snyk; the run advances to the next stage (publish/sign/lock), surfacing any further issues per the bake loop.
Generated with Claude Code