Skip to content

[oadp-dev] public velero ref 1.18.1 to match openshift/velero replace #2229

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.

Sign up for GitHub

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

Open
openshift-cherrypick-robot wants to merge 1 commit into
base: oadp-dev
Choose a base branch
from
+1 −1
Open

[oadp-dev] public velero ref 1.18.1 to match openshift/velero replace #2229

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion go.mod
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ require (
github.com/hashicorp/go-multierror v1.1.1
github.com/kubernetes-csi/external-snapshotter/client/v6 v6.3.0
github.com/stretchr/testify v1.11.1
github.com/vmware-tanzu/velero v1.14.0
github.com/vmware-tanzu/velero v1.18.1
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Jun 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

`Check github.com/vmware-tanzu/velero v1.18.1 for:

  1. Known vulnerabilities on osv.dev
  2. License type and compatibility for Apache-2.0 downstream projects
  3. Whether v1.18.1 is a stable (non-pre-release, non-yanked) tag/release`

💡 Result:

As of June 1, 2026, here is the information for Velero v1.18.1: 1) Known Vulnerabilities: A search of the Open Source Vulnerabilities (OSV) database does not yield specific vulnerabilities indexed for Velero v1.18.1 [1][2][3]. 2) License Type and Compatibility: Velero is licensed under the Apache License 2.0 [1][4][5]. This is a permissive license that is generally highly compatible with downstream projects [6]. It allows for commercial use, modification, distribution, and private use [6]. Apache 2.0 is compatible with many other open-source licenses, including GPLv3, though it is incompatible with GPLv2 due to specific patent retaliation clauses [6]. Downstream projects utilizing Velero should ensure they comply with the attribution requirements of the Apache 2.0 license (e.g., maintaining notice files) [6]. 3) Release Status: Velero v1.18.1 is a stable, non-pre-release, and non-yanked official release [1][7][8]. It was published on May 19, 2026, and is listed as a standard tag in the official repository [7][8].

Citations:

Require CI evidence for SBOM/provenance/signing for the Velero v1.18.1 bump before merge.

  • osv.dev: no specific vulnerabilities indexed for github.com/vmware-tanzu/velero v1.18.1.
  • License: Velero is Apache-2.0 (permissive; downstreams must satisfy Apache 2.0 notice/attribution requirements).
  • Release integrity: v1.18.1 is a stable, non-pre-release, non-yanked release.

Missing from the PR/CI evidence: confirmation that your build produces SBOM/provenance attestations and that released artifacts are signed (Sigstore/cosign) per your supply-chain guidelines.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@go.mod` at line 42, Add CI evidence showing SBOM/provenance and artifact
signing for the dependency bump of github.com/vmware-tanzu/velero v1.18.1
declared in go.mod: update CI pipeline to generate an SBOM (e.g., using syft),
produce provenance attestations (e.g., in-toto or sigstore/rekor entries), and
sign built artifacts and attestations with cosign, then attach or link the
generated SBOM, provenance attestation, and cosign signatures to the PR/CI run;
ensure the CI job names and artifacts are clearly referenced in the PR so
reviewers can verify the Velero v1.18.1 release has SBOM/provenance/signing
evidence.

golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56
google.golang.org/api v0.256.0
gopkg.in/yaml.v3 v3.0.1
Expand Down