Skip to content
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.

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

fix(helm): update chart nextcloud to 5.5.6 #34

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 31, 2024

This PR contains the following updates:

Package Update Change
nextcloud (source) patch 5.5.2 -> 5.5.6

Release Notes

nextcloud/helm (nextcloud)

v5.5.6

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

What's Changed

Full Changelog: nextcloud/helm@nextcloud-5.5.5...nextcloud-5.5.6

v5.5.5

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

What's Changed

New Contributors

Full Changelog: nextcloud/helm@nextcloud-5.5.4...nextcloud-5.5.5

v5.5.4

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

What's Changed

Full Changelog: nextcloud/helm@nextcloud-5.5.3...nextcloud-5.5.4

v5.5.3

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

What's Changed

Full Changelog: nextcloud/helm@nextcloud-5.5.2...nextcloud-5.5.3


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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.

Copy link

github-actions bot commented Aug 31, 2024

--- HelmRelease: default/nextcloud Deployment: default/nextcloud

+++ HelmRelease: default/nextcloud Deployment: default/nextcloud

@@ -28,13 +28,13 @@

         php-config-hash: ed0e8e1a6c704392bdc7ac88be76273cfa95c6fa671770ed92809661ad6a77d4
         nginx-config-hash: 18dd8f905a93ed27f032e9ae68084222ed7e5926f7144cda17b979780f4da54b
         hooks-hash: 9525c2748a6c7cd0e28ec740623d0b3fa5a75c83b51ccfd136bc89c76737b204
     spec:
       containers:
       - name: nextcloud
-        image: nextcloud:29.0.4-fpm-alpine
+        image: nextcloud:29.0.6-fpm-alpine
         imagePullPolicy: IfNotPresent
         env:
         - name: POSTGRES_HOST
           value: postgres16-rw.database.svc.cluster.local
         - name: POSTGRES_DB
           value: nextcloud

Copy link

github-actions bot commented Aug 31, 2024

--- kubernetes/apps/default/nextcloud/app Kustomization: flux-system/nextcloud HelmRelease: default/nextcloud

+++ kubernetes/apps/default/nextcloud/app Kustomization: flux-system/nextcloud HelmRelease: default/nextcloud

@@ -14,13 +14,13 @@

       chart: nextcloud
       interval: 15m
       sourceRef:
         kind: HelmRepository
         name: nextcloud
         namespace: flux-system
-      version: 5.5.2
+      version: 5.5.6
   dependsOn:
   - name: cloudnative-pg
     namespace: database
   install:
     remediation:
       retries: 3

@renovate renovate bot force-pushed the renovate/nextcloud-5.x branch from 7f7220d to 69cac9e Compare September 5, 2024 22:36
@renovate renovate bot changed the title fix(helm): update chart nextcloud to 5.5.3 fix(helm): update chart nextcloud to 5.5.4 Sep 5, 2024
@renovate renovate bot force-pushed the renovate/nextcloud-5.x branch from 69cac9e to a46e817 Compare September 12, 2024 19:53
@renovate renovate bot changed the title fix(helm): update chart nextcloud to 5.5.4 fix(helm): update chart nextcloud to 5.5.6 Sep 12, 2024
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