feat: Bump to 35.0.1 of nextcloud and migrate to Silo from Minio - #889
Merged
Merged
Conversation
I checked and found no breaking changes from 34. thus should be safe to go to 35 I also already upgraded my setup Signed-off-by: V. Aretakis <4048920+varet80@users.noreply.github.com>
Co-authored-by: varet80 <4048920+varet80@users.noreply.github.com>
Collaborator
Author
|
Minio decided to remove all images last week, I will need to update this test to another system like seaweedfs or similar. Will evaluate and proceed with updates. |
Signed-off-by: V. Aretakis <4048920+varet80@users.noreply.github.com>
varet80
changed the title
wrenix
enabled auto-merge (squash)
September 30, 2026 07:07
wrenix
approved these changes
Sep 30, 2026
wrenix
disabled auto-merge
September 30, 2026 07:09
1 task
valeninki
pushed a commit
to valeninki/k8s
that referenced
this pull request
Sep 30, 2026
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [nextcloud](https://nextcloud.com/) ([source](https://github.com/nextcloud/helm)) | minor | `9.3.0` -> `9.4.0` | --- >⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>nextcloud/helm (nextcloud)</summary> ### [`v9.4.0`](https://github.com/nextcloud/helm/releases/tag/nextcloud-9.4.0) [Compare Source](nextcloud/helm@nextcloud-9.3.0...nextcloud-9.4.0) A file sharing server that puts the control and security of your own data back into your hands. #### What's Changed - feat: Bump to 35.0.1 of nextcloud and migrate to Silo from Minio by [@​varet80](https://github.com/varet80) in [#​889](nextcloud/helm#889) **Full Changelog**: <nextcloud/helm@nextcloud-9.3.0...nextcloud-9.4.0> </details> --- ### Configuration 📅 **Schedule**: 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNDAuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE0MC4xIiwidGFyZ2V0QnJhbmNoIjoiazBzIiwibGFiZWxzIjpbImRlcGVuZGVuY2llcyIsImhvbGQtc3RvcmFnZS1hdWRpdCIsIm5leHRjbG91ZCJdfQ==--> Co-authored-by: Kerem <valenmortus@protonmail.com> Reviewed-on: https://git.valentinus.dev/valeninki/k8s/pulls/10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have upgraded Nextcloud to 35.0.1
Meanwhile I found Minio removed all their images (docker) from public domain, and a test was failing
migrated to Silo which is a fork of minio.
Actions taken:
I checked and found no breaking changes from 34. thus should be safe to go to 35
I also already upgraded my setup
Chart.yamlaccording to semver.