Repository navigation
chore: increase maximum supported NC version (37) - #42
Merged
Merged
Conversation
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
oleksandr-nc
force-pushed
the
chore/increase-maximum-supported-nc-version-37
branch
from
September 8, 2026 15:22
95f9ba9 to
74d8352
Compare
oleksandr-nc
deleted the
chore/increase-maximum-supported-nc-version-37
branch
September 8, 2026 16:18
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.
Bumps
max-versionfrom 35 to 37 in bothappinfo/info.xml(release/CPU-tagged) andappinfo/info-latest.xml, and bumps the app versions to 1.2.3 / 2.1.3 accordingly.Without this,
test-deploydeclares itself incompatible with Nextcloud 36 and the upcoming 37, even though the deploy test itself works there.Verified locally against Nextcloud 36.0.0 dev with AppAPI master on a HaRP daemon (
docker-install, FRP): the admin "Test deploy" dialog passes 6/6 checks - register, image pull, container started, heartbeat, init step, enabled - using the CPU imageghcr.io/nextcloud/test-deploy:release. The container reportspytorch package version: 2.8.0+cpu/Running on CPUandConnect to Nextcloud was successful.