publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #4261

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

Tested:

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

• increase version of aio app #4316
• Add information about virtual machines #4274
• Add a jellyfin community-container #4267
• 💥[breaking] - update aio-local-ai to v2 #3906 update to v2.0.0 szaimen/aio-local-ai#10 (comment)
• update mastercontainer to php8.3 #4318
• update nextcloud container to php8.2 #4320
• update Nextcloud to 28.0.3 #4321
• remove 28 upgrade hint from AIO interface #4322
• nextcloud - set maintenance_window_start #4324
• set provenance to true nextcloud-releases/all-in-one#45
• apache - drop SetEnv proxy-sendcl 1 #4323
• secure imaginary with imaginary_key #4325
• caddy community container - allow to access host.docker.internal #4326
• Disable Apache proxy buffering #4343
• d55723d
• Test: update to Nextcloud 28 #3888 (comment)

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)
• increase the version number in https://github.com/nextcloud/all-in-one/blob/main/php/templates/containers.twig#L19
• build new images. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-build-new-containers https://github.com/nextcloud-releases/all-in-one/actions/runs/8202221000
• 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)
• 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 (check if set provenance to true nextcloud-releases/all-in-one#45 works)
• 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
• 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 two weeks and see if new bugs get reported and don't merge any PR into the main branch of this repo in the meantime! (until 21.03.)
• 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)
• 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

[matteoipri]

I upgraded my test installation from 7.13.1 stable to 8.0.0 beta and everything seems to still work as expected.
The installation has been done towards the end of January directly to version 28.
This latest update brought me from N 28.0.1 to 28.0.3.

I want to migrate an existing installation done with nextcloud/docker (now at 28.0.3) to nextcloud/all-in-one. Is it safe to do it now with the beta channel, or should I pin my old installation at 28.0.3 and wait for the stable release of all-in-one v8.0.0?

[szaimen]

Following https://github.com/nextcloud/all-in-one/blob/main/migration.md should be possible from old docker v28.0.3 to AIO v8.0.0. The stable release is planned for 22.03. so you should have 11 days or longer to do the migration.