Tighten release picker action gating #183

New issue

Closed

opened 2026-04-12 19:29:29 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-04-12 19:29:29 +00:00

Problem

The release picker still exposes a flat action surface without an explicit gating policy.

Today it always offers open, copy, and delete, even though release state and forge capabilities may imply different valid actions for drafts, prereleases, or repos without delete support.

Expected

Define explicit per-entry release action gating rules for the picker surface.

That should cover at least:

whether Delete is always shown or only when the forge/repo state supports it
whether draft/prerelease state changes the visible action set
whether unavailable actions are hidden or disabled
how the picker refreshes after destructive actions

Notes

This is the release analogue to PR manage gating, but for the simpler release picker surface.

## Problem The release picker still exposes a flat action surface without an explicit gating policy. Today it always offers `open`, `copy`, and `delete`, even though release state and forge capabilities may imply different valid actions for drafts, prereleases, or repos without delete support. ## Expected Define explicit per-entry release action gating rules for the picker surface. That should cover at least: - whether `Delete` is always shown or only when the forge/repo state supports it - whether draft/prerelease state changes the visible action set - whether unavailable actions are hidden or disabled - how the picker refreshes after destructive actions ## Notes This is the release analogue to PR manage gating, but for the simpler release picker surface.

barrettruth commented

2026-04-12 21:39:28 +00:00

Closing this because the product direction is to keep picker actions flat rather than introduce per-entry release action gating. Any remaining release-picker UX problems should be tracked as narrower delete behavior, refresh, or capability-reporting bugs instead.