#127: Mattermost Renovate

General MR

Summary

This is largely a noop update. minio and gluon were already at the requested versions in the renovate ticket (and helm dependency update produced no change). The postgresql-10.3.5 version in question here was also already present, but the tarball for it in ironbank had changed. However there is no substantive difference in the content of the tarball in the previous version and this one. The only change is that the new version uses unix line endings and the previous version uses dos line endings.

I've tested the previous version and the upgrade path to this one and shown no issues on my local.

Relevant logs/screenshots

N/A

Linked Issue

Closes #127 (closed)

Upgrade Notices

N/A

changed milestone to %2.29.0

assigned to @akesterson

added teamStorage & Collaboration label

added 1 commit

• 54a5377c - WIP

Compare with previous version

added 7 commits

• 54a5377c...347c2503 - 6 commits from branch main
• 9ae2e6ba - WIP

Compare with previous version

added 1 commit

• 6ab6370f - WIP

Compare with previous version

added 1 commit

• 13c94617 - WIP

Compare with previous version

added 1 commit

• d9fb004b - #127 (closed) : Update postgresql chart

Compare with previous version

marked this merge request as ready

changed title from Draft: WIP to Mattermost Renovate

changed the description

requested review from @dchen, @michaelmartin, @chris.oconnell, @kershaw.jacob, @samvongsay, and @benjamin.starks

added statusreview label

changed title from Mattermost Renovate to #127: Mattermost Renovate

marked this merge request as draft

removed statusreview label

Pulling this from review pending the release of a potential upstream bugfix to see if we can pull that in at the same time.

marked this merge request as ready

added statusreview label

Since this is a no-op. I'd say, lets just close this one out. @chris.oconnell @andrewshoell ?

Is something going to trigger renovate again on this if we do close it out? The packaged tgz file is the source of truth, so I'm wondering why the IB image would differ.

Just wanting to make sure we aren't in some strange loop here that will come back again.

I say we go ahead and accept it. Regardless of how meaningful the change is, it is still a change. My comment re it being a NOOP is more for changelog, testing and validation purposes. But renovate will not care about that, it will just see the difference.

seems like it might be a helm thing - https://github.com/roboll/helmfile/issues/1918

because the upstream seems to be a copy of the bitnami repo we put inside this that hasn't been updated in quite some time ours is 11.11.0 and the upstream is 16.3.0.

I don't think this update matters. Not that it matters much either, but just for the sake of understanding i'm curious if @kershaw.jacob did the helm dep update on a dos-based shell in this renovate !209 (merged)

added 5 commits

• d9fb004b...b6f31d4a - 4 commits from branch main
• 9211ca5b - #127 (closed) : Update postgresql chart

Compare with previous version

closed