#8682·all-in-one

publish new images after recent PRs are merged and tested

Author: szaimenCreated Sep 11, 2026Updated Sep 18, 2026

Labelsoverview

Follow up to https://github.com/nextcloud/all-in-one/issues/8677

(add the most recent ticket for a new release here)

Tested:

(add PRs below that are potentially breaking and need to be well tested)

Tasks to do for new release:

make sure to merge any Helm Chart Updates PR before continuing with the list below (https://github.com/nextcloud/all-in-one/pulls?q=is%3Apr+is%3Aopen+helm+)
increase the version number in https://github.com/nextcloud/all-in-one/blob/main/php/templates/includes/aio-version.twig
build new images. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-build-new-containers
do a last smoke test using the develop channel (See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-test-things-correctly)
test if collabora opens
Run E2E test and wait for it to finish. See https://github.com/nextcloud/all-in-one/actions/workflows/playwright-on-workflow-dispatch.yml
deploy from develop to beta. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-promote-builds-from-develop-to-beta
tag a new release here on github which fits the version number (and use vX.Y.Z as tag and title + Beta, use the autogenerated changelog. Important: also add the included Nextcloud version manually into the body of the release, e.g. Nextcloud 26.0.2 is included but new instances can install Nextcloud 27 directly) and make it a pre release and create a Discussion in the Releases section for it.
rename next milestone to the same version number
create a new milestone that is called next
move all open issues/PRs to that new milestone
post in all issues and discussions that were fixed/implemented that this is now released with the new beta version and post how to switch to the beta channel (e.g. This is now released with X.Y.Z Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel)
wait a week and see if new bugs get reported and don't merge any PR into the main branch of this repo in the meantime!
if not, publish to latest as describe below; if yes simply close this milestone and create a new one that includes the bugfixes and starts from the beginning of this guide
deploy from beta to latest. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-promote-builds-from-beta-to-latest
Merge the automated YAML updates PR if there should be one (https://github.com/nextcloud/all-in-one/pulls?q=is%3Apr+is%3Aopen+yaml)
change the pre-release to be a stable and the latest release and remove Beta from the title (and adjust the changelog if multiple Beta version have been pushed in the meantime without a stable release - the changelog must include all changes since the latest stable release)
close the old milestone
close related discussion that announced the new beta release at https://github.com/nextcloud/all-in-one/discussions/categories/releases
close this ticket

Source: nextcloud/all-in-one

View original on GitHub View discussion on GitHub