Add dry run support to the release workflow #198

New Issue

MrUnknownDE · 2026-04-05T20:37:25+02:00

MrUnknownDE commented

2026-04-05 20:37:25 +02:00

Originally created by @dfunkt on 12/30/2025

specific workflow name via run_name variable
provides a "fake" tag to the manifest creation step (default 1.0.0, can be modified)
added to the scheduled cleanup action

Suggested in https://github.com/dani-garcia/vaultwarden/pull/6626#issuecomment-3697577078
I left the artifacts & containers attestation enabled, can be removed if deemed unnecessary.
This could be modified to also support PRs, perhaps allowing for test images specific to that PR (could be done now or at a later date)

*Originally created by @dfunkt on 12/30/2025* - specific workflow name via `run_name` variable - provides a "fake" tag to the manifest creation step (default 1.0.0, can be modified) - added to the scheduled cleanup action Suggested in https://github.com/dani-garcia/vaultwarden/pull/6626#issuecomment-3697577078 I left the artifacts & containers attestation enabled, can be removed if deemed unnecessary. This could be modified to also support PRs, perhaps allowing for test images specific to that PR (could be done now or at a later date)

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#198