dsh-update-notifier

LIMITATIONS

Known limitations

- **It asks; it does not verify.** Once you approve, the upgrade is the agent's to run. A failure is visible in the session, but this plugin neither retries it nor checks afterwards that the new version is really installed. - **Only registry-installed plugins are seen.** A plugin linked from a local checkout, or built into dsh, has no package under the profile's `node_modules` and is skipped silently — no bubble, no log line. - **Only the `latest` dist-tag is consulted.** There is no support for pinned ranges, `next`/`beta` channels, or holding a package back at a major version; a plugin whose newest release you never want should use `exclude`. - **One bubble at a time.** While a bubble waits for an answer the hourly checks skip — and `/check-updates` refuses with "an upgrade question is already open" — so anything published meanwhile is picked up on the first cycle after you answer. - **A decline is keyed to that exact version**, not to "anything up to it": if the registry's `latest` moves to a different version that still beats yours — including a lower one after an unpublish — you are asked again. - The bubble needs a session that dsh can attach a question to. Registry failures, degraded loader state, and an unwritable state file all degrade to logging; only two things disable the plugin outright — no plugin loader on the context, and a profile dir it cannot locate — and it says which in the log.