fix(web): mute routine notices and update actions - #141
Merged
leoisadev1 merged 9 commits intoSep 2, 2026
Conversation
The launch toast said "Updates Available: 2 providers" with a filled Update button, so it was unclear which CLIs would change. Name the providers in the description and use the same outline action T3 Code now uses for routine update notices.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
vouch:unvouched
Match T3 Code's muted update UI. The launch toast and per-environment Update buttons use outline instead of a filled accent. Leave toast copy unchanged; T3 closed the naming change.
EgerDev
changed the title
Port pingdotgg#9063. Routine update buttons and indicators use outline and sidebar neutrals instead of accent fills. Warning and error colors stay.
EgerDev
changed the title
Greptile SummaryThis change reduces the visual prominence of routine provider-update, composer, and desktop update notices while preserving clear warning and error treatments. Focused component coverage confirmed that update actions, settings links, retries, dismissals, and failure feedback remain available. Confidence Score: 5/5Safe to merge: no blocking failure remains in the updated notification and update-control flows. No blocking failure remains.
 T-Rex LogsWhat T-Rex did
Reviews (5): Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." | Re-trigger Greptile |
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Routine update notices use the same strong accent treatment as primary actions. Informational and successful composer banners also use semantic colors even though they do not require attention.
T3 Code made the same visual change in pingdotgg/t3code#9063.
What changed
infoandsuccesscomposer banners.The Akeru UI does not have the upstream release-notes version label, so that line does not apply.
UI
Before
After
Verification
vp test run apps/web/src/components/ProviderUpdateLaunchNotification.logic.test.ts apps/web/src/components/ProviderUpdatePrimaryNotification.test.tsx apps/web/src/components/ProviderUpdateEnvironmentRows.test.tsx apps/web/src/components/chat/ComposerBannerStack.test.tsx— 56 passedModel: grok-4.6 and gpt-5.6-sol
Harness: Grok Build and Codex in T3 Code