Repository navigation
fix(ci): downgrade upload-artifact to v4.5.0 to fix glob resolver - #27
Merged
Merged
Conversation
actions/upload-artifact v4.6.2 (ea165f8d) has a broken glob resolver that fails to match files via absolute paths on current GitHub-hosted runners. The file exists at $GITHUB_WORKSPACE/sbom-runtime.json (17768 bytes confirmed by the Verify step in run 24250664647) but the upload step reports "No files were found with the provided path". Pinning to v4.5.0 (6f51ac03) which uses @actions/glob v0.5.x with the working resolver. The download-artifact steps are already at v4.3.0 (d3f86a10) from the previous fix and remain compatible. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA GitHub Actions workflow configuration was updated by changing the pinned version of the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
✨ 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 |
This was referenced Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
actions/upload-artifactv4.6.2 (ea165f8d) has a broken glob resolver that fails to match files via absolute paths on current GitHub-hosted runners. The SBOM file is confirmed present at$GITHUB_WORKSPACE/sbom-runtime.json(17,768 bytes, verified by the diagnostic step added in #26) but the upload step reports "No files were found with the provided path".Downgrading to v4.5.0 (
6f51ac03), which uses@actions/globv0.5.x with a working resolver.Changes
ea165f8d(v4.6.2) →6f51ac03(v4.5.0)d3f86a10(v4.3.0) from fix(ci): repair silent SBOM generation failure in python-sbom workflow #25 — no change needed; v4.5.0 upload + v4.3.0 download are compatibleEvidence
From run 24250664647 (PR #26, after anchoring to
$GITHUB_WORKSPACE):File exists, path matches, glob fails — consistent with a resolver bug in v4.6.2.
Note on version label
The current SHA was annotated
# v4.6.2(correct — it does resolve to v4.6.2, not v3). The glob breakage is a regression in that release, not a version mismatch.Testing
sbom-runtime.jsonscan-runtimeandlicense-compliancejobs receive the artifact and complete🤖 Generated with Claude Code
Summary by CodeRabbit