Skip to content

chore(deps): update helm release connect to v2.4.3 - #1890

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/connect-2.4.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/connect-2.4.x

Conversation

@renovate

@renovate renovate Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
connect (source) HelmChart patch 2.4.2 → 2.4.3

Release Notes

1Password/connect-helm-charts (connect)

v2.4.3

Compare Source

A Helm chart for deploying 1Password Connect and the 1Password Connect Kubernetes Operator


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@claude

claude Bot commented Oct 22, 2026

Copy link
Copy Markdown
  • Risk: LOW — patch bump (2.4.2 → 2.4.3) of the 1Password Connect chart. Blast radius is limited to the 1password namespace (Connect API server for secrets; operator is disabled here).
  • Breaking changes: none found. The GitHub release page has only the generic chart description. The compare view (4 commits, 5 files) shows no code diff, but the commit messages say: "Bump images to pull in latest security patches" (PR chore(deps): update dependency fluxcd/flux2 to v0.31.1 #301) and "Prepare Connect chart release v2.4.3" (PR chore(deps): update pre-commit hook pre-commit/pre-commit-hooks to v4.3.0 #302). I couldn't view the file-level diff because GitHub timed out rendering it, so I can't rule out a values or template change.
  • Repo usage: cluster/apps/1password/connect/app/helm-release.yaml only sets connect.create, credentialsName, credentialsKey, serviceType: ClusterIP and operator.create: false. An image bump is unlikely to touch any of these.
  • Action needed: none, safe to merge on green. After the merge, check that the 1password-connect pods roll over to the new images and become Ready.

@renovate
renovate Bot force-pushed the renovate/connect-2.4.x branch from 780d517 to 0262a5a Compare October 27, 2026 01:00
@claude

claude Bot commented Oct 27, 2026

Copy link
Copy Markdown
  • Risk: LOW — patch bump (2.4.2 → 2.4.3) of the 1Password Connect chart. Blast radius is limited to secret delivery via Connect (the operator is disabled here).
  • Breaking changes: none found. Upstream release notes are essentially empty, and the GitHub file-level diff would not load ("taking too long to generate"), so I could not confirm Chart.yaml/values/template changes. What I could see is the commit list: "Bump images to pull in latest security patches" (PR chore(deps): update dependency fluxcd/flux2 to v0.31.1 #301) plus the release prep commit (PR chore(deps): update pre-commit hook pre-commit/pre-commit-hooks to v4.3.0 #302), 5 files changed. That points to image tag bumps only.
  • Repo usage checked: cluster/apps/1password/connect/app/helm-release.yaml sets only connect.create, credentialsName, credentialsKey, serviceType and operator.create: false. None of these were mentioned as renamed or removed, but that is unverified given the unreadable diff.
  • Action needed: none, safe to merge on green. The pods will roll to new images, so expect a brief Connect restart; check that ExternalSecrets/consumers recover afterwards.

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.

0 participants