Fixing an alert and updating your app
Every alert opens onto the same guide: what the advisory is, why it matters, the exact command to run, and how to tell VibeBeacon the fix landed.
Read the alert
Open an alert from the alerts list or from an app page. The alert page names the advisory in plain language, says how serious it is, and says how confident the match is: an exact or range match means your app runs an affected version, while a name-only match is news about a component you use, with no version match confirming your app is actually affected.
Run the command, or paste the prompt
When a fix is known, the alert page shows the exact shell command, for example npm install next@14.2.25. Copy it and run it, or copy the AI prompt underneath it and paste it into Cursor, Claude Code or whatever tool you use. It is the same prompt the instant alert email sends, so both point your AI tool at the same fix.
No fix yet
Test first on a major version bump
A patch or minor upgrade is usually safe to run and re-upload straight away. A major version bump can change behaviour, so test it before you upload the new manifest. There is no rush: the alert stays open, calmly, until you are ready.
Re-upload, and the alert closes itself
Run the CLI command again, or use the MCP tool, or drag the new vibebeacon.json onto the app page. Keep the app name the same, or pass the same --name, so the upload lands on the same app rather than creating a new one. Once the new manifest no longer shows the affected version, the alert resolves on its own. Nothing needs to be closed by hand.
Snooze, acknowledge or resolve
Acknowledge
Says you have read it. It stays open and stays on the dashboard, but drops out of the digest until something changes.
Snooze 7 days
Hides it for a week, then it comes back open. For a fix that has to wait for the next sprint.
Resolve
Marks it done by hand. If the next manifest still shows the affected version, it reopens rather than staying quietly wrong.
Acknowledge and snooze both keep the alert open; they only change how loudly it asks for attention. Resolving is the only one that says the fix landed, and it is also what a clean re-upload does for you automatically.
News-only alerts
A name-only alert means a vendor post or news item mentioned something in your stack with no version data attached. Nothing confirms your app is affected. Read it, decide whether it applies to how you use that component, and acknowledge or resolve it either way. It carries no upgrade command because there is nothing specific to run.
More on how alerts work
Severity, match confidence, and what triggers an instant email versus a digest are covered in Alerts and digests. The manifest format itself, including what a name change does and does not do, is in Manifest format.
- Read the alert, run the command or paste the prompt.
- Test it, especially for a major version bump.
- Re-upload with the same app name. The alert closes itself.
- Snooze or acknowledge if the fix has to wait; resolve if you fixed it by hand.