Add Nextcloud 35 development image workflow - #46
Draft
henmohr wants to merge 1 commit into
Draft
Conversation
Signed-off-by: henmohr <henriquemohr@redes.ufsm.br>
henmohr
force-pushed
the
agent/nextcloud-35-development
branch
from
August 17, 2026 20:22
b5ecbf4 to
563b391
Compare
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
1 participant
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.
What changed
latest-masterdaily archive and verifies its SHA-512 checksumpostgresql-client, which providespg_dumpghcr.io/librecodecoop/nextcloud-docker-app:35forlinux/amd64Why
Nextcloud 35 is still a development release and does not have an official
nextcloud:35-fpmimage. This keeps the development image separate from the existing release workflow and prevents changes to the web image or current tags.Validation
actionlint .github/workflows/nextcloud-35-development.ymllinux/amd64with cache-only output