Detect major dependency version bumps #571

Merged
justusbunsi merged 6 commits from refs/pull/571/head into main 2023-11-27 18:36:47 +00:00

6 Commits

Author SHA1 Message Date
42ea751c46 Merge branch 'main' into 409-detect-major-version-bumps 2023-11-27 18:35:56 +00:00
a1fe73bbb7 Revert "Intentionally break the build to show how it looks"
This reverts commit bb9cb2668657c97cdd4ac54505f6c6a494319343.
2023-11-18 14:36:13 +01:00
db60b5969b Revert "Intentionally break the build - part 2"
This reverts commit 7f57151c54c28acb1bd9f5a749408307e799c447.
2023-11-18 14:36:09 +01:00
7f57151c54 Intentionally break the build - part 2
Signed-off-by: justusbunsi <sk.bunsenbrenner@gmail.com>
2023-11-18 14:33:35 +01:00
bb9cb26686 Intentionally break the build to show how it looks
Signed-off-by: justusbunsi <sk.bunsenbrenner@gmail.com>
2023-11-18 14:31:39 +01:00
e4da2e1b6d Detect major dependency version bumps
As seen in #507 and #569, there is no guarantee for us that minor
dependency updates are actually minor updates for the dependent
application itself. The Chart version might be minor - and therefore
automatically merged when build is green - but the used Docker image
inside the Chart could still be a major version change.

To effectively prevent such automerge when the application major version
changes, there is now a test file that has the currently used major
versions hard-coded. In case of an actual major bump, this file has to
be adjusted.

Looking at `redis-cluster`, there might be several major Chart versions
with the same major application version.

This PR is related to #409 but does not fully resolve it.

Signed-off-by: justusbunsi <sk.bunsenbrenner@gmail.com>
2023-11-18 14:18:54 +01:00