Skip to content

fix(ui): make stack update indicator actionable - #1545

Open
thedancingdeveloper wants to merge 203 commits into
moghtech:mainfrom
thedancingdeveloper:fix/931-stack-update-action
Open

fix(ui): make stack update indicator actionable#1545
thedancingdeveloper wants to merge 203 commits into
moghtech:mainfrom
thedancingdeveloper:fix/931-stack-update-action

Conversation

@thedancingdeveloper

Copy link
Copy Markdown

Summary

  • reuse the existing typed redeploy confirmation from the stack page for authorized /stacks table indicators
  • preserve the existing DeployStack request and updated-service selection behavior
  • render update availability as non-button status UI when the user lacks execute permission
  • keep the change scoped to stacks

Closes #931.

Root cause

The table passes small to StackUpdateAvailable, which previously sent the component into a status-only branch. That branch rendered an ActionIcon without an onClick, link, or action, so the control looked clickable but could only display a hover card.

Behavior

  • users with execute permission: clicking the table icon opens the same typed Redeploy confirmation used on the stack page
  • users without execute permission: the icon remains a hoverable update-status indicator but is rendered as a non-interactive ThemeIcon
  • full stack page: existing check/update actions and payloads remain unchanged

Testing

  • cd client/core/ts && corepack yarn install --frozen-lockfile && corepack yarn build && corepack yarn link
  • cd ui && corepack yarn link komodo_client && corepack yarn install --frozen-lockfile && corepack yarn build
  • git diff --check

The UI production build succeeds. Existing dependency peer warnings and Vite chunk-size warnings are unchanged.

mbecker20 and others added 28 commits July 17, 2026 14:44
…tech#1528)

Git providers send push webhooks for every branch and Komodo filters
them server side (docs: Automate > Webhooks > Branch Filtering), so a
push to a non-matching branch is routine operation, not a failure. It
was surfaced through the generic 'Failed at running webhook' warn,
indistinguishable from genuine failures, and a repo with active bot
branches (e.g. Renovate) produces hundreds of these warns per day.

Rename ExtractBranch::verify_branch to branch_matches, returning
Ok(false) on a mismatch (logged at debug) so handlers skip quietly,
matching the existing silent webhook_enabled=false skip. Branch
EXTRACTION failures (e.g. a ref-less payload on a named-branch
listener) still return Err and reach the warn, preserving the
misconfiguration signal.
…t corrupt service detection (moghtech#1529)

Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>
Co-authored-by: Maxwell Becker <49575486+mbecker20@users.noreply.github.com>
@mbecker20
mbecker20 changed the base branch from 2.3.0 to main July 28, 2026 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants