Replies: 4 comments 5 replies
|
That seems like an oversight. I didn't know dependabot supported docker compose, that should fix it. Would you be able to send us a pull request? Thanks |
|
Actually, I think it doesn't work because the docker-compose files are templated with Jinja tags, so dependabot isn't able to update images in them. We'll have to update the images manually. They are also pinned in the GitHub workflows (and maybe in other CI providers we offer as option) |
|
Sorry about that, I only tested on a generated project without any Jinja tags. Didn't even think ti would be problematic considering other package ecosystems work fine. Oh I see now there are additional redis images, even |
|
Yea... I know, I didn't think of that either, and I'm quite used to this kind of issues 😢 Would you mind sending us another PR to fix it? Can we use the latest version of is it against their license? I know they re-licensed in 2024 but I didn't follow closely enough |
|
According to this licence explanation that dual licence switch was for version 7.4 and after community backlash they introduced three licence model in version 8.0, but no BSD 3 licence like before. My understanding was that this would not affect the use case for the cookie cutter template, but I'm definitely not an expert in the licensing department so I would appreciate if someone else makes the decision here. |
|
I guess the choice is:
|
|
For me, just replace Redis by Valkey |
|
Yea, Valkey was also on my mind. Let's first get to a supported version as per #6118 which should be an easy one and then migrate |
Uh oh!
There was an error while loading. Please reload this page.
I noticed redis 6 (6.2) is EOL since February this year -> https://redis.io/docs/latest/operate/rs/installing-upgrading/product-lifecycle/#endoflife-schedule
Is docker image pinned to redis 6 for some reason or is this just an oversight? Seems like we would also need to configure "docker-compose" package-ecosystem in dependabot for these updates.
All reactions