Is this a general issue which should be reflected in the upgrade path tool (e.g. introduce an intermediate step at 18.4.x) or is it still considered safe to skip 18.4, when correctly performing the database migrations after each step in the upgrade path?
Lukas Grossar (bfe3bb76) at 13 Oct 06:27
Lukas Grossar (60a2469a) at 13 Oct 06:27
Merge branch 'chore/switch_component' into 'main'
... and 1 more commit
Now that components/package!12 has been merged we can switch back to the official component
Lukas Grossar (bfe3bb76) at 13 Oct 06:22
ci: use official component
Now that components/package!12 has been merged we can switch back to the official component
Lukas Grossar (3578cd0b) at 13 Oct 06:18
ci: use official component
@jdrpereira I switched to CI_COMMIT_REF_SLUG in 39d5651c.
Lukas Grossar (39d5651c) at 25 Sep 10:47
feat: use CI_COMMIT_REF_SLUG as default image tag
I've also considered replacing the default of CI_COMMIT_REF_NAME for IMAGE_TAG, since it fails whenever a / is used in the branch name, but I wanted to discuss that in this MR first.
A potential replacement might be CI_COMMIT_REF_SLUG