Skip to content

Bump Helm Chart and Dagger Version => v1.82.0#2856

Merged
migmartri merged 1 commit intomainfrom
create-pull-request/patch
Mar 14, 2026
Merged

Bump Helm Chart and Dagger Version => v1.82.0#2856
migmartri merged 1 commit intomainfrom
create-pull-request/patch

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

A new Chainloop release is available! Bumping Helm Chart reference and Dagger version to v1.82.0

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@migmartri migmartri merged commit 2c2e9ec into main Mar 14, 2026
3 checks passed
@migmartri migmartri deleted the create-pull-request/patch branch March 14, 2026 18:09
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

3 issues found across 16 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="deployment/chainloop/Chart.yaml">

<violation number="1" location="deployment/chainloop/Chart.yaml:10">
P2: Use a patch bump for the Helm chart version instead of incrementing the minor version.</violation>
</file>

<file name="deployment/chainloop/values.yaml">

<violation number="1" location="deployment/chainloop/values.yaml:141">
P2: Bump `deployment/chainloop/Chart.yaml`'s patch version alongside this values change, or Helm consumers can miss the updated package because the chart version stays `1.343.0`.</violation>
</file>

<file name="vuln-control-plane-migrations-amd64.json">

<violation number="1" location="vuln-control-plane-migrations-amd64.json:23">
P0: The new `control-plane-migrations:v1.82.0-amd64` artifact is built with vulnerable Go stdlib `go1.25.7`, and the scan already reports two high-severity CVEs with fixes available in `1.25.8`/`1.26.1`. Releasing this image would ship known vulnerabilities.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

},
"helpUri": "https://github.com/anchore/grype",
"help": {
"text": "Vulnerability CVE-2026-25679\nSeverity: high\nPackage: stdlib\nVersion: go1.25.7\nFix Version: 1.25.8,1.26.1\nType: go-module\nLocation: /atlas\nData Namespace: nvd:cpe\nLink: [CVE-2026-25679](https://nvd.nist.gov/vuln/detail/CVE-2026-25679)",
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Mar 14, 2026

Choose a reason for hiding this comment

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

P0: The new control-plane-migrations:v1.82.0-amd64 artifact is built with vulnerable Go stdlib go1.25.7, and the scan already reports two high-severity CVEs with fixes available in 1.25.8/1.26.1. Releasing this image would ship known vulnerabilities.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At vuln-control-plane-migrations-amd64.json, line 23:

<comment>The new `control-plane-migrations:v1.82.0-amd64` artifact is built with vulnerable Go stdlib `go1.25.7`, and the scan already reports two high-severity CVEs with fixes available in `1.25.8`/`1.26.1`. Releasing this image would ship known vulnerabilities.</comment>

<file context>
@@ -0,0 +1,227 @@
+              },
+              "helpUri": "https://github.com/anchore/grype",
+              "help": {
+                "text": "Vulnerability CVE-2026-25679\nSeverity: high\nPackage: stdlib\nVersion: go1.25.7\nFix Version: 1.25.8,1.26.1\nType: go-module\nLocation: /atlas\nData Namespace: nvd:cpe\nLink: [CVE-2026-25679](https://nvd.nist.gov/vuln/detail/CVE-2026-25679)",
+                "markdown": "**Vulnerability CVE-2026-25679**\n| Severity | Package | Version | Fix Version | Type | Location | Data Namespace | Link |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| high  | stdlib  | go1.25.7  | 1.25.8,1.26.1  | go-module  | /atlas  | nvd:cpe  | [CVE-2026-25679](https://nvd.nist.gov/vuln/detail/CVE-2026-25679)  |\n"
+              },
</file context>
Fix with Cubic

type: application
# Bump the patch (not minor, not major) version on each change in the Chart Source code
version: 1.342.1
version: 1.343.0
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Mar 14, 2026

Choose a reason for hiding this comment

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

P2: Use a patch bump for the Helm chart version instead of incrementing the minor version.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At deployment/chainloop/Chart.yaml, line 10:

<comment>Use a patch bump for the Helm chart version instead of incrementing the minor version.</comment>

<file context>
@@ -7,9 +7,9 @@ description: Chainloop is an open source software supply chain control plane, a
 type: application
 # Bump the patch (not minor, not major) version on each change in the Chart Source code
-version: 1.342.1
+version: 1.343.0
 # Do not update appVersion, this is handled automatically by the release process
-appVersion: v1.81.2
</file context>
Suggested change
version: 1.343.0
version: 1.342.2
Fix with Cubic

registry: ghcr.io
repository: chainloop-dev/chainloop/control-plane
tag: "v1.81.2"
tag: "v1.82.0"
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Mar 14, 2026

Choose a reason for hiding this comment

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

P2: Bump deployment/chainloop/Chart.yaml's patch version alongside this values change, or Helm consumers can miss the updated package because the chart version stays 1.343.0.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At deployment/chainloop/values.yaml, line 141:

<comment>Bump `deployment/chainloop/Chart.yaml`'s patch version alongside this values change, or Helm consumers can miss the updated package because the chart version stays `1.343.0`.</comment>

<file context>
@@ -138,7 +138,7 @@ controlplane:
     registry: ghcr.io
     repository: chainloop-dev/chainloop/control-plane
-    tag: "v1.81.2"
+    tag: "v1.82.0"
 
 
</file context>
Fix with Cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant