You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Publish: decide all-or-nothing promotion for signed releases #387
Backlog from #379 review. The publish matrix uses fail-fast: false, so bot, API and WebUI can each be promoted even if a sibling build fails in the same run. Decide whether signed releases should promote all-or-nothing. Not blocking #379.
This needs an owner decision first, so it isn't ready for a bot to work on. Once the owner picks all-or-nothing promotion or not, the fix is one small publish workflow change plus a test, about 200 changed lines or less. The updater and image signing code are out of scope.
For now, publishing is all or nothing. A release promotes every image together or none of them, because the changes are too tightly linked to update one part without the others.
The docs should note that these may become individual releases later. That's not part of this issue.
Scope stays as stated above: one small publish workflow change plus a test, about 200 changed lines or less, with the updater and image signing out of scope.
Activity
jatmn commentedon Oct 28, 2026
Work guideline
This needs an owner decision first, so it isn't ready for a bot to work on. Once the owner picks all-or-nothing promotion or not, the fix is one small publish workflow change plus a test, about 200 changed lines or less. The updater and image signing code are out of scope.
jatmn commentedon Oct 28, 2026
Owner decision
For now, publishing is all or nothing. A release promotes every image together or none of them, because the changes are too tightly linked to update one part without the others.
The docs should note that these may become individual releases later. That's not part of this issue.
Scope stays as stated above: one small publish workflow change plus a test, about 200 changed lines or less, with the updater and image signing out of scope.