skillshare v0.30.5 Release Notes

TL;DR

1. Choose your own update schedule. skillshare updates off stops automatic release checks and update notices in the CLI and web dashboard, including cached notices, dialogs and version badges.
2. Manual checks and upgrades still work. Use skillshare updates check, the web dashboard's manual check, or skillshare upgrade whenever you are ready. Checks for upstream changes to installed resources are unchanged.
3. Keep the preference in config or the environment. The global updates.auto_check setting defaults to true; SKILLSHARE_AUTO_UPDATE_CHECK overrides it without changing the saved value.

Control automatic version checks

Disable automatic CLI and built-in skill version checks and their notifications:

skillshare updates off
skillshare updates --json

To turn them back on, run skillshare updates on. The preference is global, including when the command is run from a project directory.

You can also set it in the global config.yaml:

updates:
  auto_check: false

Or override it for a process and its children:

SKILLSHARE_AUTO_UPDATE_CHECK=false skillshare status

The environment takes precedence over config; if neither is set, automatic checks remain enabled. No migration is required.

Web dashboard

In global mode, Settings → General → Updates offers the same automatic-check switch and a manual check. The global preference also applies to projects, where the Web switch is read-only. An environment override also locks the switch. A manual check can still open Update now while automatic checks are disabled; a failed check does not report that everything is current or retain stale success actions.

The dashboard refreshes the local preference every five seconds without checking releases, so a preference changed in another terminal also hides existing automatic prompts.

Desktop controls require a separate app release that includes skillshare-app#126. Updating the CLI alone does not disable checks in older desktop builds; this release does not publish or update the desktop app.

Thanks to @LloydPowell771 for explaining the monthly rollout workflow and requesting this option in #846. Implemented in #847.