fix(outdated-build): allow dismissing outdated build banner #14558
+14
−6
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.
Fixes #14424
First time contributor checklist
Contributor checklist
Fixes #1234syntaxDescription
This PR adds a dismiss action to the outdated build banner, allowing users to temporarily hide the banner during the current app session.
Previously, the banner could only be resolved by updating the app, which meant it would remain visible even when users were already aware of the warning or unable to update immediately. This change introduces a lightweight dismissal mechanism using local Compose state, without altering any existing expiry logic or update behavior.
The banner will reappear on the next app restart if the build is still outdated, ensuring that users continue to receive the reminder while avoiding unnecessary friction within a single session.
Testing
This change addresses the UX concern described in #14424 while keeping the warning behavior intact.