github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-15 23:02:03 -05:00
Code Issues 2.9k Packages Projects Releases Wiki Activity

[PR #921] [MERGED] fix(vaultwarden): update outdated image version #16233

New Issue
Closed
opened 2026-07-14 23:15:18 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-07-14 23:15:18 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/921
Author: @nerkoux
Created: 6/9/2026
Status: ✅ Merged
Merged: 7/7/2026
Merged by: @Siumauricio

Base: canary ← Head: fix/vaultwarden-version

📝 Commits (1)

  • a5f0185 fix(vaultwarden): update outdated image version

📊 Changes

2 files changed (+2 additions, -2 deletions)

View changed files

📝 blueprints/vaultwarden/docker-compose.yml (+1 -1)
📝 meta.json (+1 -1)

📄 Description

What is this PR about?

Update the Vaultwarden template from vaultwarden/server:1.34.3 to vaultwarden/server:1.36.0.

The current template uses an outdated Vaultwarden version. During testing, deployments using 1.34.3 experienced issues with recent Bitwarden clients, including the browser extension and Android application. After upgrading to 1.36.0 and redeploying the template, authentication and synchronization worked correctly.

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

N/A

Screenshots or Videos

Successful Deployment

dokploy2 dokploy1

Testing Performed

  • Successfully deployed the updated template in Dokploy
  • Verified web access through the configured domain
  • Verified authentication using the Bitwarden browser extension
  • Verified authentication using the Bitwarden Android application
  • Verified vault synchronization between clients

Changes

  • Updated Vaultwarden image version from 1.34.3 to 1.36.0
  • Updated template metadata version accordingly

🔄 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/Dokploy/templates/pull/921 **Author:** [@nerkoux](https://github.com/nerkoux) **Created:** 6/9/2026 **Status:** ✅ Merged **Merged:** 7/7/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `fix/vaultwarden-version` --- ### 📝 Commits (1) - [`a5f0185`](https://github.com/Dokploy/templates/commit/a5f0185c324826a816e6f4ee45383ffff1a25c66) fix(vaultwarden): update outdated image version ### 📊 Changes **2 files changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/vaultwarden/docker-compose.yml` (+1 -1) 📝 `meta.json` (+1 -1) </details> ### 📄 Description ## What is this PR about? Update the Vaultwarden template from `vaultwarden/server:1.34.3` to `vaultwarden/server:1.36.0`. The current template uses an outdated Vaultwarden version. During testing, deployments using `1.34.3` experienced issues with recent Bitwarden clients, including the browser extension and Android application. After upgrading to `1.36.0` and redeploying the template, authentication and synchronization worked correctly. ## Checklist Before submitting this PR, please make sure that: * [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template * [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. * [ ] I have added tests that demonstrate that my correction works or that my new feature works. ## Issues related (if applicable) N/A ## Screenshots or Videos ### Successful Deployment <img width="1920" height="949" alt="dokploy2" src="https://github.com/user-attachments/assets/421c52f5-4c57-4481-852b-44ae04a9f3b9" /> <img width="1914" height="949" alt="dokploy1" src="https://github.com/user-attachments/assets/2439b524-502a-4ed6-a2d8-fb1695694bed" /> ### Testing Performed * Successfully deployed the updated template in Dokploy * Verified web access through the configured domain * Verified authentication using the Bitwarden browser extension * Verified authentication using the Bitwarden Android application * Verified vault synchronization between clients ### Changes * Updated Vaultwarden image version from `1.34.3` to `1.36.0` * Updated template metadata version accordingly --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-07-14 23:15:18 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#16233
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?