Skip to content

chore: increase maximum supported NC version (37) - #42

Merged
oleksandr-nc merged 1 commit into
mainfrom
chore/increase-maximum-supported-nc-version-37
Sep 8, 2026
Merged

oleksandr-nc merged 1 commit into
mainfrom
chore/increase-maximum-supported-nc-version-37

Conversation

@oleksandr-nc

@oleksandr-nc oleksandr-nc commented Sep 8, 2026 •

Copy link
Copy Markdown
Contributor

Bumps max-version from 35 to 37 in both appinfo/info.xml (release/CPU-tagged) and appinfo/info-latest.xml, and bumps the app versions to 1.2.3 / 2.1.3 accordingly.

Without this, test-deploy declares 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 image ghcr.io/nextcloud/test-deploy:release. The container reports pytorch package version: 2.8.0+cpu / Running on CPU and Connect to Nextcloud was successful.

Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
@oleksandr-nc
oleksandr-nc force-pushed the chore/increase-maximum-supported-nc-version-37 branch from 95f9ba9 to 74d8352 Compare September 8, 2026 15:22
@oleksandr-nc
oleksandr-nc merged commit c7d4540 into main Sep 8, 2026
4 checks passed
@oleksandr-nc
oleksandr-nc deleted the chore/increase-maximum-supported-nc-version-37 branch September 8, 2026 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant