ObolNetwork / ObolNetwork/helm-charts

Dependency Dashboard

Open
#71 0 comments 0 reactions 1 assignee View on GitHub

@apham0001 is already working on this.

Since Feb 17, 2025.

platform
Dominant language
Go Template
Stars
3
Forks
5
PR merge metrics
No merged PRs in 30d

Description

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.

PR Edited (Blocked)

The following updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox below.

Detected Dependencies

github-actions (6)
.github/workflows/add-issue-to-project.yml (1)
  • actions/add-to-project v1.0.2@244f685bbc3b7adfa8466e08b698b5577571133e
.github/workflows/label-issues.yml (1)
  • actions/github-script v9@3a2844b7e9c422d3c10d287c895573f7108da1b3
.github/workflows/lint.yml (5)
  • actions/checkout v6@de0fac2e4500dabe0009e67214ff5f5447ce83dd
  • azure/setup-helm v5@dda3372f752e03dde6b3237bc9431cdc2f7a02a2
  • actions/setup-python v6@a309ff8b426b58ec0e2a45f0f869d46889d02405
  • pre-commit/action v3.0.1@2c7b3805fd2a0fd8c1884dcaebf91fc102a13ecd
  • python 3.14
.github/workflows/release.yml (7)
  • actions/checkout v6@de0fac2e4500dabe0009e67214ff5f5447ce83dd
  • azure/setup-helm v5@dda3372f752e03dde6b3237bc9431cdc2f7a02a2
  • helm/chart-releaser-action v1.7.0@cae68fefc6b5f367a0275617c9f83181ba54714f
  • actions/checkout v6@de0fac2e4500dabe0009e67214ff5f5447ce83dd
  • azure/setup-helm v5@dda3372f752e03dde6b3237bc9431cdc2f7a02a2
  • actions/checkout v6@de0fac2e4500dabe0009e67214ff5f5447ce83dd
  • peaceiris/actions-gh-pages v4@4f9cc6602d3f66b9c108549d475ec49e8ef4d45e
.github/workflows/test.yml (3)
  • actions/checkout v6@de0fac2e4500dabe0009e67214ff5f5447ce83dd
  • helm/kind-action v1.14.0@ef37e7f390d99f746eb8b610417061a60e82a6cc
  • azure/setup-helm v5.0.0@dda3372f752e03dde6b3237bc9431cdc2f7a02a2
.github/workflows/version-bump.yml (1)
  • actions/checkout v6@de0fac2e4500dabe0009e67214ff5f5447ce83dd
regex (23)
.github/helm-ci-values/values-aztec-node.yaml (1)
  • aztecprotocol/aztec 4.2.0
.github/helm-ci-values/values-charon-cluster.yaml (1)
  • obolnetwork/charon v1.9.4
.github/helm-ci-values/values-charon.yaml (1)
  • obolnetwork/charon v1.9.4
.github/helm-ci-values/values-openclaw.yaml (1)
  • ghcr.io/obolnetwork/openclaw 2026.4.8 → [Updates: 2026.4.21]
charts/aztec-node/Chart.yaml (1)
  • aztecprotocol/aztec 4.2.0
charts/aztec-node/values.yaml (1)
  • aztecprotocol/aztec 4.2.0
charts/charon-cluster/Chart.yaml (1)
  • obolnetwork/charon 1.9.4
charts/charon-cluster/values.yaml (1)
  • obolnetwork/charon v1.9.4
charts/charon-relay/Chart.yaml (1)
  • obolnetwork/charon 1.9.4
charts/charon-relay/values.yaml (1)
  • obolnetwork/charon v1.9.4
charts/charon/Chart.yaml (1)
  • obolnetwork/charon 1.9.4
charts/charon/values.yaml (1)
  • obolnetwork/charon v1.9.4
charts/dv-pod/Chart.yaml (1)
  • obolnetwork/charon 1.9.4
charts/dv-pod/templates/prometheus-deployment.yaml (1)
  • prom/prometheus v3.11.1 → [Updates: v3.11.2]
charts/dv-pod/templates/statefulset.yaml (1)
  • sigp/lighthouse v8.1.3
charts/dv-pod/templates/statefulset.yaml (1)
  • consensys/teku 26.4.0
charts/dv-pod/templates/statefulset.yaml (2)
  • gcr.io/prysmaticlabs/prysm/validator v7.1.3
  • gcr.io/prysmaticlabs/prysm/validator v7.1.3
charts/dv-pod/templates/statefulset.yaml (1)
  • statusim/nimbus-eth2 multiarch-v26.3.1
charts/dv-pod/templates/statefulset.yaml (1)
  • statusim/nimbus-validator-client multiarch-v26.3.1
charts/dv-pod/templates/statefulset.yaml (1)
  • chainsafe/lodestar v1.41.1 → [Updates: v1.42.0]
charts/dv-pod/templates/statefulset.yaml (2)
  • busybox 1.37.0
  • busybox 1.37.0
charts/dv-pod/values.yaml (1)
  • obolnetwork/charon v1.9.4
charts/openclaw/values.yaml (1)
  • ghcr.io/obolnetwork/openclaw 2026.4.8 → [Updates: 2026.4.21]

  • Check this box to trigger a request for Renovate to run again on this repository

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.