fix(web): source control update toasts return on each new release - #230
Merged
Conversation
Git and GitHub CLI toasts only fired for two hard-coded security versions, and closing one silenced it until Threadlines shipped a higher number. Plain newer releases never toasted at all. The server now keys every update advisory on the latest release instead of the security floor, and the client shows a toast for any newer release. Closing it hides it until the next release ships, the same way the Claude and Codex update prompts already behave. Security floors still change the wording and tone, but no longer gate the toast.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
vouch:trusted
badcuban
enabled auto-merge (squash)
September 5, 2026 07:57
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
1 participant
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.
Git and GitHub CLI update toasts only fired for two hard-coded security versions, and closing one silenced it until Threadlines shipped a higher number. Plain newer releases never toasted at all.
The server now keys every update advisory on the latest release instead of the security floor, and the client shows a toast for any newer release. Closing it hides it until the next release ships, matching how the Claude and Codex update prompts already behave. Security floors still change the wording ("update recommended" vs "update available") and the toast tone, but no longer gate the toast.
Note: existing saved dismissals used the old key format, so users still behind will see the toast once more after this ships.
Verified:
vp fmt,vp lint,vp run typecheck, server and web unit tests for the touched modules, and the full web browser suite.