Repository navigation
fix(ci): use exact filename for upload-artifact path - #30
Conversation
The glob pattern sbom-*.json (and its absolute variants) triggers a
known bug in upload-artifact@v4's glob resolver when the workspace
path contains repeated directory segments (here: .claude/.claude —
the repo is named .claude, so GitHub sets GITHUB_WORKSPACE to
/home/runner/work/.claude/.claude).
Since the generate step produces exactly one file, sbom-runtime.json,
no glob is needed. Using the exact filename bypasses the glob resolver
entirely. The path retains the ${{ github.workspace }} prefix to avoid
the separate CWD != GITHUB_WORKSPACE issue in reusable workflows.
Note: the SHAs supplied in the previous PR description were incorrect
(ff15f030 = v3.2.1, not v4.6.2; 95815c38 has no release tag). No
action version changes in this commit — that can be a follow-up once
the functional bug is confirmed fixed.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 53 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 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 |
Summary
Replaces the glob pattern
sbom-*.jsonwith the exact filenamesbom-runtime.json. The glob triggers a known bug inupload-artifact@v4's resolver when the workspace path contains repeated directory segments — here, the repo is named.claude, so GitHub setsGITHUB_WORKSPACEto/home/runner/work/.claude/.claude/, and the repeated component causes the glob to fail even when the file exists.Since the generate step produces exactly one file, no glob is needed. Using the exact filename bypasses the resolver bug entirely. The
${{ github.workspace }}prefix is retained to avoid the separate CWD ≠GITHUB_WORKSPACEfailure in reusable workflows.What has been tried and ruled out
sbom-*.json(relative glob)${{ github.workspace }}/sbom-*.json${{ github.workspace }}/sbom-*.jsonwith v4.5.0sbom-*.json(relative, no prefix)${{ github.workspace }}/sbom-*.json${{ github.workspace }}/sbom-runtime.json(exact filename)Note on action version SHAs
The previous PR description supplied two incorrect SHAs (
ff15f030= v3.2.1;95815c38= untagged commit). No action version changes in this PR. A follow-up to upgradeupload-artifactfrom v4.5.0 to the current v7.x line can land after the functional bug is confirmed fixed.Testing
scan-runtimeandlicense-compliancejobs receive the artifact🤖 Generated with Claude Code