-
Notifications
You must be signed in to change notification settings - Fork 419
zot/2.1.13-r0: cve remediation #77697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔢 Build Failed: Dependency Version Mismatch
Build Details
Root Cause Analysis 🔍The dependency github.com/sigstore/[email protected] has an incompatible module path structure. The go.mod file specifies a post-v2 module path 'github.com/sigstore/timestamp-authority/v2' but the version tag v2.0.3 doesn't match this module path convention. Go modules with major version v2+ require the major version to be included in the module path. 🔍 Build failure fix suggestionsFound similar build failures that have been fixed in the past and analyzed them to suggest a fix: Similar PRs with fixesSuggested ChangesFile: zot.yaml
Replacement: Content: Click to expand fix analysisAnalysisThe similar fix shows a clear pattern for handling Go module v2+ dependency issues. When a package has upgraded to v2.x.x and uses the "/v2" module path suffix, the dependency specification in go/bump must be updated to include both the old v1.x path (for compatibility) and the new v2.x path with the correct module path format. The fix involved adding two entries: one for the legacy path with a v1.x version and another for the new v2 module path with the v2.x version. Click to expand fix explanationExplanationThe current error occurs because the timestamp-authority package has migrated to Go modules v2+ convention, which requires the major version to be included in the module path. The go.mod file in the upstream repository specifies the module path as 'github.com/sigstore/timestamp-authority/v2', but the dependency is being referenced as 'github.com/sigstore/[email protected]' without the '/v2' suffix. By changing the dependency specification to 'github.com/sigstore/timestamp-authority/[email protected]', we align with the correct module path format that Go expects for v2+ modules. This matches the pattern seen in the containerd fix where the v2 module path was explicitly specified with the '/v2' suffix. Click to expand alternative approachesAlternative Approaches
Was this comment helpful? Please use 👍 or 👎 reactions on this comment. |
|
This vulnerability remediation is stale and no longer needed. 👋 Advisory CGA-c92q-vh28-wcfp has the latest event type of "pending-upstream-fix" View with: 🔀 v2 advisory logic would not have closed this PR: Found 4 advisories, but 2 of them are not resolved (CGA-x848-9mpc-h56j, CGA-vx7p-fcwr-98f7). |
<!--ci-cve-scan:must-fix: GHSA-4qg8-fj49-pxjh-->
cd8de93 to
61c5f5c
Compare
|
This vulnerability remediation is stale and no longer needed. 👋 Advisory CGA-c92q-vh28-wcfp has the latest event type of "pending-upstream-fix" View with: |
|
This vulnerability remediation is stale and no longer needed. 👋 Advisory CGA-cg35-jq58-qrrx has the latest event type of "PENDING_UPSTREAM_FIX" View with: |
zot/2.1.13-r0: fix GHSA-4qg8-fj49-pxjh
Advisory data: https://github.com/wolfi-dev/advisories/blob/main/zot.advisories.yaml
"Breadcrumbs" for this automated service
Inspected git repositories: https://github.com/project-zot/[email protected]