▲ 103 ▼ Vaultwarden security update Feb 10 2026 (github.com) submitted 9 months ago by megaman@discuss.tchncs.de to c/selfhosted@lemmy.world 14 comments fedilink hide all child comments GHSA-h265-g7rm-h337 (Publication in process, waiting for CVE assignment) This vulnerability would allow an authenticated attacker that is part of an organization to access items from collections to which the attacker does not belong
[–] Natanox@discuss.tchncs.de 2 points 9 months ago (4 children) Renovate? permalink fedilink source parent hideshow 4 child comments replies: [–] tofu@lemmy.nocturnal.garden 6 points 9 months ago I have all my compose stacks in git. They're deployed from their git repos with Komodo. Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there's a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It's a great semi automatic way to handle updates without giving up control. There's a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo permalink fedilink source parent [–] qaz@lemmy.world 1 point 9 months ago (2 children) It's a bot to create PR's with dependency updates permalink fedilink source parent hideshow 2 child comments replies: [–] Natanox@discuss.tchncs.de 2 points 9 months ago (1 child) Might be a stupid question, but how are PR's connected to your server deployment? permalink fedilink source parent hideshow 1 child comment replies: [–] tofu@lemmy.nocturnal.garden 2 points 8 months ago Copying my other comment. It opens PRs to change the tag from the docker image. I have all my compose stacks in git. They’re deployed from their git repos with Komodo. Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control. There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo permalink fedilink source parent
[–] tofu@lemmy.nocturnal.garden 6 points 9 months ago I have all my compose stacks in git. They're deployed from their git repos with Komodo. Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there's a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It's a great semi automatic way to handle updates without giving up control. There's a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo permalink fedilink source parent
[–] qaz@lemmy.world 1 point 9 months ago (2 children) It's a bot to create PR's with dependency updates permalink fedilink source parent hideshow 2 child comments replies: [–] Natanox@discuss.tchncs.de 2 points 9 months ago (1 child) Might be a stupid question, but how are PR's connected to your server deployment? permalink fedilink source parent hideshow 1 child comment replies: [–] tofu@lemmy.nocturnal.garden 2 points 8 months ago Copying my other comment. It opens PRs to change the tag from the docker image. I have all my compose stacks in git. They’re deployed from their git repos with Komodo. Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control. There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo permalink fedilink source parent
[–] Natanox@discuss.tchncs.de 2 points 9 months ago (1 child) Might be a stupid question, but how are PR's connected to your server deployment? permalink fedilink source parent hideshow 1 child comment replies: [–] tofu@lemmy.nocturnal.garden 2 points 8 months ago Copying my other comment. It opens PRs to change the tag from the docker image. I have all my compose stacks in git. They’re deployed from their git repos with Komodo. Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control. There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo permalink fedilink source parent
[–] tofu@lemmy.nocturnal.garden 2 points 8 months ago Copying my other comment. It opens PRs to change the tag from the docker image. I have all my compose stacks in git. They’re deployed from their git repos with Komodo. Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control. There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo permalink fedilink source parent