Skip to content

Conversation

@Javex
Copy link

@Javex Javex commented Dec 7, 2025

Description of the change

When overriding image.tag the version label should also show the correct version. Previously, the label would always be AppVersion, even if the user had provided a different image tag (thus deploying a different Nextcloud version).

With this change, the version is always first derived from the image tag and only from AppVersion if not tag was provided. For the "nextcloud.image" helper this was already the case, now the "version" label on all resources also does this.

Benefits

Version label always represents deployed image tag.

Possible drawbacks

If user's have specified a different version through the image tag then all of their resources' version label will change, causing a re-deployment. However, no difference in functionality should be observed and no user action is needed. That is, this is a backwards-compatible change.

Applicable issues

N/A

Additional information

Checklist

When overriding `image.tag` the version label should also show the
correct version. Previously, the label would always be AppVersion, even
if the user had provided a different image tag (thus deploying a
different Nextcloud version).

With this change, the version is always first derived from the image tag
and only from AppVersion if not tag was provided. For the
"nextcloud.image" helper this was already the case, now the "version"
label on all resources also does this.

Signed-off-by: Florian Ruechel <code@inexplicity.de>
@wrenix
Copy link
Collaborator

wrenix commented Dec 11, 2025

You drop th support for image.flavor

Signed-off-by: Florian Ruechel <code@inexplicity.de>
@Javex Javex force-pushed the app-version-image-tag branch from b9ebfc6 to e9a214a Compare December 13, 2025 02:22
@Javex
Copy link
Author

Javex commented Dec 13, 2025

@wrenix Good catch, thanks! Fixed now

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.

2 participants