I've created a new protected environment that will only apply the secrets to protected branches (main). This should silence some zizmor lints.
I had to remove the top-level env, as the environment seems to only apply to the jobs. Rather than duplicate the HAVE_* variables, I just changed the workflow to check the *_REPO variables only, and updated the comment to mention it.
🔄 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/7004
**Author:** [@dani-garcia](https://github.com/dani-garcia)
**Created:** 3/23/2026
**Status:** ✅ Merged
**Merged:** 3/23/2026
**Merged by:** [@dani-garcia](https://github.com/dani-garcia)
**Base:** `main` ← **Head:** `use-protected-environment`
---
### 📝 Commits (1)
- [`e2b4860`](https://github.com/dani-garcia/vaultwarden/commit/e2b48609f747f884439fdbe9b132af5982838fa1) Use protected CI environment
### 📊 Changes
**1 file changed** (+31 additions, -28 deletions)
<details>
<summary>View changed files</summary>
📝 `.github/workflows/release.yml` (+31 -28)
</details>
### 📄 Description
I've created a new protected environment that will only apply the secrets to protected branches (`main`). This should silence some zizmor lints.
I had to remove the top-level env, as the environment seems to only apply to the jobs. Rather than duplicate the `HAVE_*` variables, I just changed the workflow to check the `*_REPO` variables only, and updated the comment to mention it.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/7004
Author: @dani-garcia
Created: 3/23/2026
Status: ✅ Merged
Merged: 3/23/2026
Merged by: @dani-garcia
Base:
main← Head:use-protected-environment📝 Commits (1)
e2b4860Use protected CI environment📊 Changes
1 file changed (+31 additions, -28 deletions)
View changed files
📝
.github/workflows/release.yml(+31 -28)📄 Description
I've created a new protected environment that will only apply the secrets to protected branches (
main). This should silence some zizmor lints.I had to remove the top-level env, as the environment seems to only apply to the jobs. Rather than duplicate the
HAVE_*variables, I just changed the workflow to check the*_REPOvariables only, and updated the comment to mention it.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.