[PR #5551] [CLOSED] Add multi-level version tags to docker releases #3634

New issue

Closed

opened 2026-03-03 10:05:04 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 10:05:04 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/5551
Author: @RoboMagus
Created: 2/6/2025
Status: ❌ Closed

Base: main ← Head: docker_version_tags

📝 Commits (1)

3b7de4f Add multi-level version tags to docker releases

📊 Changes

1 file changed (+13 additions, -1 deletions)

View changed files

📝 .github/workflows/release.yml (+13 -1)

📄 Description

As I consider Vaultwarden to be a vital part of my selfhosted services I do not like to roll the dice and auto update my Docker containers and sticking to the latest label. However, manually updating the container version every time a new patch release is out is too manual.

This PR bridges the gap between the two. The rationale is well explained here, but the gist of it is that having the option to pin the docker tag to major, or major.minor allows users enable automatic updates up to the level they are comfortable with. I.e. automatically staying secure for security patches, but not automatically updating when a breaking change is introduced.

What this PR does:
When a new version is released, e.g. 1.34.5, and if this tag complies with SemVer formatting, the following tags are also added to the docker images:

1: Major version
1.34: Major.Minor version

(In case it does not match the SemVer formatting, nothing is added)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/dani-garcia/vaultwarden/pull/5551 **Author:** [@RoboMagus](https://github.com/RoboMagus) **Created:** 2/6/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docker_version_tags` --- ### 📝 Commits (1) - [`3b7de4f`](https://github.com/dani-garcia/vaultwarden/commit/3b7de4fd74c5004915a0f7180e93fdee91339005) Add multi-level version tags to docker releases ### 📊 Changes **1 file changed** (+13 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+13 -1) </details> ### 📄 Description As I consider Vaultwarden to be a vital part of my selfhosted services I do not like to roll the dice and auto update my Docker containers and sticking to the `latest` label. However, manually updating the container version every time a new _patch_ release is out is too manual. This PR bridges the gap between the two. The rationale is well explained [here](https://medium.com/@mccode/using-semantic-versioning-for-docker-image-tags-dfde8be06699), but the gist of it is that having the option to pin the docker tag to `major`, or `major.minor` allows users enable automatic updates up to the level they are comfortable with. I.e. automatically staying secure for security patches, but not automatically updating when a breaking change is introduced. What this PR does: When a new version is released, e.g. `1.34.5`, and if this tag complies with SemVer formatting, the following tags are also added to the docker images: - `1`: Major version - `1.34`: Major.Minor version (In case it does not match the SemVer formatting, nothing is added) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>