[PR #7033] [MERGED] Disable deployments for release env #20732

Closed
opened 2026-04-25 22:42:05 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/7033
Author: @dfunkt
Created: 3/29/2026
Status: Merged
Merged: 4/1/2026
Merged by: @dani-garcia

Base: mainHead: patch-1


📝 Commits (1)

  • f51666c Disable deployments for release env

📊 Changes

1 file changed (+6 additions, -2 deletions)

View changed files

📝 .github/workflows/release.yml (+6 -2)

📄 Description

As according to the docs:
https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/control-deployments#using-environments-without-deployments

This is useful when you want to use environments for:

Organizing secrets—group related secrets under an environment name without creating deployment records.
Access control—restrict which branches can use certain secrets via environment branch policies, without deployment tracking.
CI and testing jobs—reference an environment for its configuration without adding noise to the deployment history.


🔄 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/7033 **Author:** [@dfunkt](https://github.com/dfunkt) **Created:** 3/29/2026 **Status:** ✅ Merged **Merged:** 4/1/2026 **Merged by:** [@dani-garcia](https://github.com/dani-garcia) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`f51666c`](https://github.com/dani-garcia/vaultwarden/commit/f51666c4687eb4945a40d7126f88438cc4045c75) Disable deployments for release env ### 📊 Changes **1 file changed** (+6 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+6 -2) </details> ### 📄 Description As according to the docs: https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/control-deployments#using-environments-without-deployments > This is useful when you want to use environments for: > > Organizing secrets—group related secrets under an environment name without creating deployment records. > Access control—restrict which branches can use certain secrets via environment branch policies, without deployment tracking. > CI and testing jobs—reference an environment for its configuration without adding noise to the deployment history. --- <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-04-25 22:42:05 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#20732