Skip to content

Update valkey repository URL to OCI format#298

Open
3deep5me wants to merge 1 commit into8gears:mainfrom
3deep5me:patch-1
Open

Update valkey repository URL to OCI format#298
3deep5me wants to merge 1 commit into8gears:mainfrom
3deep5me:patch-1

Conversation

@3deep5me
Copy link
Copy Markdown

@3deep5me 3deep5me commented Feb 19, 2026

What this PR does / why we need it

Update to valkey repo to OCI format to be future proof.

Special notes for your reviewer

It makes it easier to pull the dep. chart over a proxy harbor.

Checklist

Version and Documentation

Testing and Validation

  • Ran ah lint locally without errors
  • Ran Chart-Testing: ct lint --chart-dirs charts/n8n --charts charts/n8n --validate-maintainers=false
  • Tested chart installation locally
  • Tested with example configurations in /examples directory

Summary by CodeRabbit

  • Chores
    • Chart version bumped for a patch release.
    • External dependency source switched to an OCI registry to simplify distribution.
    • Release metadata updated to reflect the repository format change.
    • No runtime or behavioral changes introduced; existing functionality remains unchanged.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 19, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: fd3c74e2-fb6c-41d1-b812-f135d404b7e2

📥 Commits

Reviewing files that changed from the base of the PR and between acbf2d9 and 5b45419.

⛔ Files ignored due to path filters (1)
  • charts/n8n/Chart.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • charts/n8n/Chart.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • charts/n8n/Chart.yaml

Walkthrough

Bumped the Helm chart version and changed the valkey dependency repository URL from HTTPS to an OCI registry in charts/n8n/Chart.yaml; updated the artifacthub.io/changes annotation. No functional code or control-flow changes.

Changes

Cohort / File(s) Summary
Chart metadata & dependency
charts/n8n/Chart.yaml
Bumped version 2.0.12.0.2; changed dependencies[name=valkey].repository from https://valkey.io/valkey-helm/ to oci://ghcr.io/valkey-io/valkey-helm; updated artifacthub.io/changes annotation text.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Update valkey repository URL to OCI format' directly and clearly summarizes the main change in the pull request—updating the Helm dependency repository URL from HTTPS to OCI format.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.

Add a .trivyignore file to your project to customize which findings Trivy reports.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
charts/n8n/Chart.yaml (2)

36-38: ⚠️ Potential issue | 🟡 Minor

artifacthub.io/changes annotation is stale — still describes the previous ingress/pathType change, not this valkey repository update.

The changes entry should be updated to reflect the dependency source change introduced by this PR.

✏️ Suggested update
  artifacthub.io/changes: |
-   - kind: changed
-     description: "Changed the ingress logic to allow different types of pathType in place of the hardcoded 'pathType: Prefix'"
+   - kind: changed
+     description: "Updated valkey dependency repository to OCI format"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@charts/n8n/Chart.yaml` around lines 36 - 38, The artifacthub.io/changes
annotation in Chart.yaml is stale; update the "changes" entry under
artifacthub.io/changes to describe the dependency source change introduced by
this PR (the valkey repository update) instead of the old ingress/pathType
note—locate the artifacthub.io/changes block and replace the current description
lines with a brief entry mentioning the dependency source update (e.g., "Changed
dependency source: updated valkey repository"), keeping the same YAML structure
and list formatting.

3-3: ⚠️ Potential issue | 🟠 Major

Chart.lock must be regenerated and chart version must be bumped after the dependency repository change.

The valkey repository has been changed from https://valkey.io/valkey-helm/ to oci://ghcr.io/valkey-io/valkey-helm/valkey, but Chart.lock still references the old HTTPS URL. This mismatch will cause helm dependency update to resolve dependencies inconsistently. Regenerate Chart.lock by running helm dependency update charts/n8n, and bump the chart version in Chart.yaml (currently 2.0.1) to signal this breaking change to downstream consumers.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@charts/n8n/Chart.yaml` at line 3, Regenerate the Helm dependency lock and
bump the chart version: update Chart.yaml's version (currently 2.0.1 — increment
it, e.g., 2.0.2) and run "helm dependency update charts/n8n" to refresh
Chart.lock so the valkey dependency uses the new OCI URL
(oci://ghcr.io/valkey-io/valkey-helm/valkey) instead of the old
https://valkey.io/valkey-helm/; commit the updated Chart.yaml and regenerated
Chart.lock.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@charts/n8n/Chart.yaml`:
- Around line 28-31: The dependency entry with name: valkey has an incorrect OCI
repository URL that includes the chart name; update the repository field from
oci://ghcr.io/valkey-io/valkey-helm/valkey to the parent OCI registry
oci://ghcr.io/valkey-io/valkey-helm so Helm will append /valkey:0.8.1 itself,
and then verify that the specified version (version: 0.8.1) actually exists in
that GHCR namespace (update version if necessary).

---

Outside diff comments:
In `@charts/n8n/Chart.yaml`:
- Around line 36-38: The artifacthub.io/changes annotation in Chart.yaml is
stale; update the "changes" entry under artifacthub.io/changes to describe the
dependency source change introduced by this PR (the valkey repository update)
instead of the old ingress/pathType note—locate the artifacthub.io/changes block
and replace the current description lines with a brief entry mentioning the
dependency source update (e.g., "Changed dependency source: updated valkey
repository"), keeping the same YAML structure and list formatting.
- Line 3: Regenerate the Helm dependency lock and bump the chart version: update
Chart.yaml's version (currently 2.0.1 — increment it, e.g., 2.0.2) and run "helm
dependency update charts/n8n" to refresh Chart.lock so the valkey dependency
uses the new OCI URL (oci://ghcr.io/valkey-io/valkey-helm/valkey) instead of the
old https://valkey.io/valkey-helm/; commit the updated Chart.yaml and
regenerated Chart.lock.

Comment thread charts/n8n/Chart.yaml
@3deep5me 3deep5me force-pushed the patch-1 branch 2 times, most recently from 142bbb6 to acbf2d9 Compare February 19, 2026 18:46
@3deep5me 3deep5me marked this pull request as ready for review February 19, 2026 18:50
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.

No issues found across 2 files

@Vad1mo
Copy link
Copy Markdown
Member

Vad1mo commented Feb 20, 2026

@3deep5me
Copy link
Copy Markdown
Author

should be fine now.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants