Skip to content

fix(apps): surface the trust reason when Update All hits a trust-gated app - #29936

Merged
KiroCrewCaptain merged 2 commits into
mainfrom
fix/29758-update-all-trust-reason
Nov 9, 2026
Merged

KiroCrewCaptain merged 2 commits into
mainfrom
fix/29758-update-all-trust-reason

Conversation

@chenmingwei23

@chenmingwei23 chenmingwei23 commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: When "Update All" hits an app that needs execution trust, tell the user that app needs trust instead of reporting a bare "Failed to update" with no reason.

Bug fix: with two updatable registry apps whose trust is not current, clicking Apps > Discover > Updates > Update All shows the banner "Failed to update: " with no dialog and no reason, and both apps stay on their old version. The per-row Update on the same rows opens the trust dialog and updates, so the reason exists but Update All never surfaces it.

Why it matters

A user who clicks Update All on apps that only need a trust grant gets a dead-end failure with no next step, even though the per-row Update makes the fix obvious. They cannot tell a trust gate apart from a real update failure, so the apps silently stay stale.

Not a goal

  • Opening the trust dialog from the batch itself. Update All is a non-interactive sequential loop; a per-app modal from it is a flow change this fix does not make. The notice points the user to the per-row Update, which already opens the dialog.
  • Auto-granting trust. No trust is granted on the user's behalf.

What changed (motivation -> approach -> change)

Observed symptom: trust-gated apps report "Failed to update" with no reason under Update All. Root cause: updateAll catches every per-app error straight into one failed list without checking isTrustDeniedError, while the per-row runUpdate already branches on exactly that code. So a trust refusal and a genuine failure are indistinguishable in the batch path.

Change: branch the batch catch the same way runUpdate does. A caught error that isTrustDeniedError recognises goes into a new needsTrust bucket; anything else stays a real failure in failed. After the loop, each trust-gated app gets its own notice line (new key pages.appsPage.update_needs_trust) naming the app and pointing to its per-row Update; genuine failures still aggregate into failed_to_update. This mirrors how consentNeeded is already surfaced per app. No app is skipped silently and no trust is auto-granted.

Backwards compatibility

Removes nothing: adds one error-bucket branch and one notice string; the existing success, failure, consent and refusal paths are unchanged.

Tests

Two tests added to website/src/pages/apps/useAppUpdates.test.tsx: a trust-gated app in a batch is surfaced with update_needs_trust and not folded into failed_to_update; and a batch with one trust block and one real failure separates the two onto their own notice lines.

Proof: PROVEN pages.appsPage.update_needs_trust tests fail with the production hunk reverted (both new tests RED on reverted production, GREEN with the fix; verified by hand since prove.py runs Python only and this is a frontend test).

Manual verification

N/A -- unit coverage exercises the batch catch branch directly against a trust-denied rejection shape; staging a real multi-app trust-gated backend batch adds nothing the unit test does not already pin.

Screenshots / video

Apps > Discover > Updates after Update All, with one trust-gated app (Crew Manager, execution trust lapsed) and one app that really fails (todo.txt). Both notice lines now show in one banner: the new update_needs_trust line names the trust-gated app with its reason instead of folding it into Failed to update.

Update All showing a trust-reason line and a failure line

The temp-screenshots/29758/ folder is for review only and will be removed after merge.

Unrelated CI notes

These red lanes are not caused by this diff (frontend hook + locale strings only); none touches their code:

  • Frontend Tests (1/2/3) -> Frontend Coverage Merge -> Coverage Gate: one root cause, src/test/ChatPage.dirStaging.test.tsx > ChatPage file-chip remove parity > the same file picked under two differently-rooted slots keeps both chips (pickedFileTokens is not slot-scoped). This is a main-only failure: the same test fails the same way on the unrelated PR fix(a11y): expose open state on three more disclosure toggles #29993 (an accessibility change that touches none of this code). That file is not in this diff and passes locally on this branch (66/66). The Coverage Gate log shows it fails closed only because frontend-test=failure (backend-test=success), so there is no coverage regression here.
  • Backend Tests (Windows) (4): a strict-xfail flake on test/scale_budget/test_catalog_budget.py from stale scale-F4 markers, main-only (it also flips on unrelated PRs); the dedicated cleanup for those markers is tracked separately. It is green on this head but flips intermittently.
  • Frontend Tests (4) (and the Frontend Coverage Merge / Coverage Gate it cascades into): src/test/framerMotionMockStableTags.test.ts > every framer-motion mock under src caches its motion components flags src/test/ChatSidebar.boardRenameOfflineScope.test.tsx. Neither file is in this diff (which touches no framer-motion code), and the gate test is byte-identical to origin/main, so this is a pre-existing main failure, not this change. The same lane fails the same way on the unrelated PRs fix: hand incident chat exits in an app pop-out to the main window #31314 and fix(dashboard): keep unsent split-view and Bot chat text across a page reload #31308.

Related Issues

Closes #29758

Sibling sweep

Swept: grep for every catch that aggregates app-update errors without an isTrustDeniedError branch in website/src/pages/apps/ and website/src/components/appstore/.
Sibling: website/src/pages/apps/useAppUpdates.ts:runUpdate -- not affected -- already branches on isTrustDeniedError (it is the pattern this fix copies).
Siblings: none -- updateAll was the only batch catch in the update path that dropped the trust code.

Pattern harvest

Rule candidate: review-prompt
Pattern: a batch/aggregate error handler swallowing a specific recoverable error code that the single-item handler beside it already branches on, hiding the reason from the user.

Checklist

  • At most two commits (one), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable) -- N/A
  • No secrets, credentials, or internal references in the diff

@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Reviewer note: this is a UI copy change. Update All now shows one notice line per trust-gated app (new key pages.appsPage.update_needs_trust, naming the app and pointing to its per-row Update) instead of folding that app into the generic "Failed to update" list. No app is skipped and no trust is auto-granted; a real update failure still shows under "Failed to update". The notice surface and layout are unchanged -- only which i18n key the existing banner is handed.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 4, 2026
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 9f7a421a44112838a0610838aec250f6f72f7161 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: the batch catch now uses the same isTrustDeniedError check as runUpdate, and a committed screenshot shows the new notice line.

Notes

  • The description opens with <!-- no-visual-delta --> but also commits a screenshot and adds a new user-visible notice line. Drop the marker so the UX lanes don't read the PR as a no-render change.
  • The notice says "Use its own Update button to allow it". That works only because updateAll is used only in DiscoverPage, which passes onTrustDenied. The batch branch skips the onTrustDenied && guard that runUpdate has. If another page reuses updateAll without that callback, the advice leads nowhere.

[DESIGN-REVIEWED] 9f7a421

Description read

[DESCRIPTION-READ] cbc967b4089752dc4e25e5c212749141bcb72a987905b13188970b4c23da9c26

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of 9f7a421a44112838a0610838aec250f6f72f7161 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

Nothing blocks. The new line says what happened and gives the next step. Confusion only appears in a mixed batch, where the banner's existing first-line heading makes the trust line look like part of the failure.

Notes

  • When a batch has both a real failure and a trust block, the "Failed to update: todo.txt" heading sits above the Crew Manager line. The blind reader said "I can't tell which app failed… Maybe both failed." Order the trust notices first, or give each notice its own line with no heading styling, so each app's outcome reads on its own.
  • "it needs your permission" doesn't say what is being allowed, so the reader would only "maybe" click the per-row Update. Name it, e.g. "{{name}} was not updated: it needs permission to run on this computer. Click its Update button to review and allow it."
  • The trust notice uses the same red error styling as a real failure, though it is a step the user can take, not an error. If the banner supports a warning or neutral tone, use it for this line.

[UX-REVIEWED] 9f7a421

Description read

[DESCRIPTION-READ] d305093e935e189992c76ca7638f9c71a2e2594df0c8d4e9d7fdd68ee00cb898

That sha256 names everything this verdict read: the PR description, plus the 4 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 9f7a421a44112838a0610838aec250f6f72f7161 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing to check.

What this change ships

Inventory (4 items) — 3 justified

Intent: when Update All hits an app that needs execution trust, the user should be told it needs permission, not just that it failed. FIX.

  1. Update All now adds a notice line for each app that needs trust, pointing the user to its own Update button — justified
  2. Apps that need trust no longer appear in the "Failed to update" list; real failures still do — justified
  3. A new update_needs_trust string added in all 14 locales — justified
  4. A review screenshot added under temp-screenshots/29758/ — rides along

[FIRST-PRINCIPLES-REVIEWED] 9f7a421

Description read

[DESCRIPTION-READ] 42cbf0cff7a2204de41830381cd2fedb72f7ff503bbd824dbafdd019d7e14b76

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 9f7a421a44112838a0610838aec250f6f72f7161 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 9f7a421

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 9f7a421a44112838a0610838aec250f6f72f7161 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 9f7a421a44112838a0610838aec250f6f72f7161 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 9f7a421

Verdict parsed from the review's SHA-scoped output markers for commit 9f7a421a44112838a0610838aec250f6f72f7161.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 9f7a421a44112838a0610838aec250f6f72f7161 false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 4, 2026
@chenmingwei23
chenmingwei23 force-pushed the fix/29758-update-all-trust-reason branch from 587fbae to 942b9a5 Compare November 4, 2026 22:15
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Addressed in 942b9a5. The blocking finding was correct: in ja, de, ru, zh-CN, ko, hi and bn the notice named a literal "Update" button, but that row button renders the translated label (components.appstore.installedAppCard.update: 更新, Aktualisieren, Обновить, 更新, 업데이트, अपडेट करें, আপডেট করুন). Each of those seven strings now uses that locale's own button label so the control it names is the one on screen. en and es/fr/it/pt already matched their button labels and are unchanged. Only the seven flagged locale values changed; {{name}} is preserved in each and catalog parity is green.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 4, 2026
@chenmingwei23
chenmingwei23 marked this pull request as ready for review November 4, 2026 23:27
@chenmingwei23
chenmingwei23 requested review from a team and KiroCrewCaptain as code owners November 4, 2026 23:27
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 6, 2026
@chenmingwei23
chenmingwei23 force-pushed the fix/29758-update-all-trust-reason branch from 942b9a5 to b429e44 Compare November 6, 2026 08:31
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Nov 6, 2026
@chenmingwei23
chenmingwei23 force-pushed the fix/29758-update-all-trust-reason branch from b429e44 to b070878 Compare November 6, 2026 08:58
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 6, 2026
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 8, 2026
@chenmingwei23
chenmingwei23 force-pushed the fix/29758-update-all-trust-reason branch from b070878 to 603aa2e Compare November 8, 2026 09:07
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 8, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this fix. The code looks right. One evidence item has to be resolved before this can merge.

  1. website/src/pages/apps/useAppUpdates.ts:220-221 and website/src/i18n/locales/en.json:6727: when Update All runs into a trust-gated app, users now read a new sentence in the Discover > Updates banner. The UX review on this head could not evaluate that sentence because no screenshot shows it. Its PASS is only a formatting downgrade, so the new user-facing text would merge without anyone seeing it rendered. Smallest fix: attach a screenshot of Apps > Discover > Updates after Update All, with one trust-gated app and one app that really fails, so both notice lines appear. This is a fork PR, so attach it through the GitHub web UI or commit it under temp-screenshots/. Then re-run the UX lane on the new head. Or, if you think a text-only notice line in an existing banner needs no screenshot, please say so in a comment and a maintainer will decide.

What the review checked on this head: the new isTrustDeniedError branch matches the one runUpdate already uses, and the local-only trust check still runs first. The only updateAll host (DiscoverPage) wires onTrustDenied and rowUpdatesInPlace, so the advice in the notice is accurate. The two new tests pass, and both fail when the hook is reverted to main. Each trust-gated app getting its own notice line, next to the existing consent and repository-trust lines, is a clean fit.

Optional, not required to merge:

  • The comment at useAppUpdates.ts:213-217 lists two non-failure outcomes. The new execution-trust case is a third one it could mention.
  • needsTrust and trustNeeded are very close names for different buckets. A name like executionTrustNeeded would be harder to mix up.
  • The UX lane left wording notes ("needs trust" may be unclear to a newcomer, and it could say which row to use). A short reply either way would help.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision readiness: action required A blocking check or review needs attention labels Nov 8, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Evidence added on head 20dbc99: temp-screenshots/29758/update-all-trust-reason.png, embedded in the PR description. It is Apps > Discover > Updates after Update All with one execution-trust-gated app (Crew Manager, 403 app_execution_denied) and one real failure (todo.txt, 500), so both notice lines render in one banner: Failed to update: todo.txt and Crew Manager needs trust to update. Use its own Update button to review and grant trust. The temp-screenshots/29758/ folder is review-only and gets removed after merge. Re-running the UX lane on this head now.

On the optional points:

  • The needs trust wording and which row to use: taken. I kept this round to the evidence the merge is blocked on and did not re-word the string, to avoid re-opening the locale/register work; the sentence already points to the row's own Update button ("Use its own Update button"). Happy to refine the copy in a follow-up if a maintainer wants a specific phrasing.
  • needsTrust vs trustNeeded: fair point that they are close. trustNeeded is main's repository-trust bucket and needsTrust is this PR's execution-trust bucket; renaming main's symbol is out of this PR's scope, so I left both as-is rather than touch code the fix does not own. A rename to something like executionTrustNeeded is a clean follow-up.
  • The comment at the catch block listing non-failure outcomes: same follow-up; I did not expand it this round to keep the diff to the behavior change plus its test and evidence.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 8, 2026
@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

Thanks for adding the screenshot. The code still looks right, and the earlier review item is resolved on this head.

Earlier item: the missing screenshot of the new banner line is fixed. temp-screenshots/29758/update-all-trust-reason.png is committed, embedded in the description, and shows this head's exact English string under Failed to update: todo.txt.

What this review checked on this head:

  • The new isTrustDeniedError branch in updateAll runs after the localOnlyTrustRepository check, so the local-only case still wins. A trust-blocked app does not land in failed and is not counted as updated.
  • The only updateAll host is DiscoverPage, which wires onTrustDenied and rowUpdatesInPlace. So the row's own Update button really does open the trust dialog, as the notice says.
  • Both new tests would fail if the hook change were reverted. The new key is present in all 13 generated locales.

What still holds this PR: PR Readiness is red on one item, the UX lane's BLOCK on this head. A maintainer needs to decide how it is answered. Context for that decision:

  • The tone half (the trust line sits in the red error banner) is existing behaviour. On main, the consent and repository-trust notices already go through the same banner. Moving only this line to a neutral surface would add a new notice channel, which is beyond this PR's goal. A short reply that says so, with a follow-up issue, fits better than building it here.
  • The wording half is in scope and cheap. The new string does not say the app was not updated, so under a failure title it reads like that failure's explanation. The shipped sibling update_needs_repository_trust already uses a clearer shape ("{{name}} was not updated, because ..."). For example: "{{name}} was not updated: its new version needs your permission to run. Click Update on its row to review and allow it." This would need the 12 locale copies too.

Optional, not required:

  • The PR description still starts with the no-visual-delta marker, says "Manual verification: N/A", and says the PR has one commit. The PR now has a screenshot from a real run and two commits. A description edit fixes this without a push.
  • The mixed-batch test in useAppUpdates.test.tsx (around line 376) uses only toContain. Asserting the exact notice with toBe, like the neighbouring test does, would pin the one-line-per-app layout.
  • needsTrust next to trustNeeded is easy to mix up. A name like executionTrustNeeded for the new bucket would help.

@KiroCrewCaptain
KiroCrewCaptain dismissed their stale review November 8, 2026 21:58

Withdrawn: every item in this review is fixed or answered on the current head (see the follow-up comment). Other holds on this PR are listed there.

@chenmingwei23
chenmingwei23 force-pushed the fix/29758-update-all-trust-reason branch from 20dbc99 to ce6be74 Compare November 8, 2026 22:18
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 8, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Updated on head ce6be74. I reworded the update_needs_trust line in every locale so it names its app and reads on its own, in plainer words. English: {name} was not updated: it needs your permission. Use its own Update button to allow it. The bn and hi strings name "the Update button" without quoting its label, so the register checks stay green. I did not touch failed_to_update or update_needs_repository_trust, added no hook callback, and added no new notice surface. The re-captured screenshot in the PR description (temp-screenshots/29758/update-all-trust-reason.png) shows the new wording with one app that needs permission and one that really fails.

On the banner concern itself: you are right that the non-error lines (needs permission, needs repository trust, needs consent) share the one red error banner, which is wider than this change. I kept that structure here to stay in scope and opened a follow-up to split the non-error lines out of the error banner: #33452. Re-running the UX lane on this head now.

kirocrew-agent added 2 commits November 8, 2026 22:42
…d app

Update All caught every per-app error into one failed_to_update list
without checking isTrustDeniedError, so an app that needs execution trust
reported a bare "Failed to update" with no reason while the per-row
Update opened the trust dialog. Branch the batch catch the same way
runUpdate does: collect trust-denied apps into their own bucket and name
each with a notice that points to its per-row Update, leaving real
failures in failed_to_update. No trust is auto-granted and no app is
dropped silently. The notice names the app and reads on its own
("was not updated: it needs your permission") so a mixed batch is
unambiguous.

Closes #29758
Evidence for the reworded pages.appsPage.update_needs_trust line: Apps >
Discover > Updates after Update All with one app that needs permission
and one genuine failure, so both notice lines render. Review-only;
temp-screenshots/29758/ is removed after merge.
@chenmingwei23
chenmingwei23 force-pushed the fix/29758-update-all-trust-reason branch from ce6be74 to 9f7a421 Compare November 8, 2026 22:53
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 8, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update All lists apps that need trust on their own line, separate from failed updates. Trust is never granted automatically. Tested.

@KiroCrewCaptain
KiroCrewCaptain enabled auto-merge (squash) November 8, 2026 23:59

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix and for the follow-up work. Nothing blocks on this head.

Earlier items: the missing screenshot is fixed. temp-screenshots/29758/update-all-trust-reason.png is committed and shows a mixed batch with this head's English string. The wording concern is fixed too: the line now says the app was not updated and names the next step in every locale. The red banner tone is deferred to #33452, and the UX lane passes on this head.

What this review checked on this head: the new isTrustDeniedError branch in updateAll runs after the localOnlyTrustRepository check, and the two error codes are disjoint, so no app lands in two buckets. A trust-blocked app is not counted as updated. DiscoverPage is the only updateAll host, and it wires onTrustDenied and rowUpdatesInPlace, so the advice to use the row's own Update button is accurate. The batch never grants trust by itself. Both new tests fail with the hook change reverted, and they use mocked promises with no timers. PR Readiness is green.

Done well: the fix reuses the predicate runUpdate already uses instead of adding a second detector, and the mixed-batch test keeps a real failure ("disk full") on the failure line, separate from the trust line.

Optional:

  • The description still opens with <!-- no-visual-delta -->, says "Manual verification N/A", and says one commit. The head has two commits and a screenshot of a real run. You can fix this with a description edit and no push.
  • The mixed-batch test uses only toContain. Asserting the full notice with toBe, as the neighbouring test does, would pin one line per app. The trust fixtures could also use the real ApiError shape (status plus a JSON body) like the local-only test.
  • needsTrust and trustNeeded are easy to mix up. A name like executionTrustNeeded and a line in the comment at useAppUpdates.ts:213-217 would help.

@KiroCrewCaptain
KiroCrewCaptain merged commit 0131154 into main Nov 9, 2026
101 checks passed
@KiroCrewCaptain
KiroCrewCaptain deleted the fix/29758-update-all-trust-reason branch November 9, 2026 00:00
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 9, 2026
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.

"Update All" fails with no reason for apps that need trust

3 participants