Skip to content

Fix main build: add missing egress endpoints to harden-runner#1213

Open
spoorcc wants to merge 2 commits into
mainfrom
claude/fix-main-build-cCB7E
Open

Fix main build: add missing egress endpoints to harden-runner#1213
spoorcc wants to merge 2 commits into
mainfrom
claude/fix-main-build-cCB7E

Conversation

@spoorcc
Copy link
Copy Markdown
Contributor

@spoorcc spoorcc commented May 16, 2026

Summary

  • Add release-assets.githubusercontent.com:443 to source-provenance.yml — needed by slsa_with_provenance to download the slsa-source-corroborator binary from GitHub releases
  • Add timestamp.githubapp.com:443 to source-provenance.yml, build.yml, and test.yml — needed by actions/attest and actions/attest-build-provenance when signing DSSE attestation wrappers
  • Add uploads.github.com:443 to the build-whl job in build.yml — needed for artifact upload

All three endpoints were blocked by the harden-runner egress policy, cascading into build and test failures on main.

Test plan

  • source-provenance workflow passes on main (both attest-source-governance and attest-source jobs)
  • build workflow passes (binary and wheel jobs complete attestation steps)
  • test workflow passes attestation step

https://claude.ai/code/session_01FzXNiF3f5iEnRPX3SWfd2A


Generated by Claude Code

claude added 2 commits May 16, 2026 22:51
…s policy

The slsa_with_provenance action downloads the slsa-source-corroborator
binary from GitHub releases, which redirects through
release-assets.githubusercontent.com. This endpoint was missing from
the harden-runner allowed list for the attest-source-governance job,
causing the egress block and failing the main build.

https://claude.ai/code/session_01FzXNiF3f5iEnRPX3SWfd2A
actions/attest and actions/attest-build-provenance call
timestamp.githubapp.com when signing DSSE attestation wrappers.
This endpoint was absent from source-provenance.yml, build.yml,
and test.yml, causing the egress block to refuse the connection.

https://claude.ai/code/session_01FzXNiF3f5iEnRPX3SWfd2A
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 16, 2026

Warning

Rate limit exceeded

@spoorcc has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 25 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 70c9af9b-2123-4e2d-ac1c-9c2f57e8ac32

📥 Commits

Reviewing files that changed from the base of the PR and between 79444c8 and 23f8ebc.

📒 Files selected for processing (3)
  • .github/workflows/build.yml
  • .github/workflows/source-provenance.yml
  • .github/workflows/test.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/fix-main-build-cCB7E

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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.

2 participants