skillshare v0.20.26 Release Notes
TL;DR
update --forceworks again — when the security audit blocked an update, the error told you to pass--force, but the flag never reached the audit check. It does now, on every update path.- Two ways to bypass the audit are closed —
install --jsonand grouped batch updates were skipping the block threshold entirely. - The dashboard stops offering buttons that cannot help — Force Retry no longer appears on failures that force cannot resolve, such as a permission error.
- Heads up — a
--forceused at install time no longer exempts that skill from the audit on later updates.
--force reaches the security audit
When an update contained a finding at or above your block threshold, Skillshare rolled it back and printed a message telling you to use --force. Passing it changed nothing: updates are staged in a temporary directory first, and the internal setting that also controlled the audit had to stay off there for the audit to run at all — which discarded your --force along with it. The only way through was --skip-audit, which turns scanning off entirely instead of letting you review findings and accept them.
--force now reaches the audit on every update path: regular skills, tracked repositories, agents, and the Force Retry button in the web dashboard.
skillshare update my-skill --force # show findings, then apply anyway
skillshare update my-skill --skip-audit # do not scan at allOne case deliberately ignores --force: if the scanner itself fails to run, the update is still rolled back. Accepting findings you have seen is not the same as proceeding when nothing could be checked.
Two paths that skipped the audit
install --json set an internal overwrite flag so it could run without prompting, and the audit read that same flag — so JSON-mode installs quietly accepted content that would have been blocked in an interactive run. Updating several skills from one repository in a single batch had the same problem.
Both are now scanned like any other install or update. If you script installs with --json and relied on them always succeeding, add --force or --skip-audit where you actually intend to bypass the check.
Clearer failures in the web dashboard
An update that failed for a reason force cannot fix — for example failed to remove existing skill: ... permission denied, caused by files owned by another user — still showed a Force Retry button. Pressing it retried with force and failed identically, with no hint of what would actually help.
Force Retry now appears only for audit blocks and for pulls that would genuinely be retried with force. Update errors also no longer quote command-line flags such as Use --force to override or --skip-audit to bypass scanning, which had no meaning on a page with no command line.
Migration guide
--force is now a per-command decision.
Previously, installing a skill with --force had the side effect of exempting it from the audit on every later update. That no longer holds: a skill installed with --force is scanned again on its next update, and needs --force (or --skip-audit) again to apply findings at or above the block threshold.
If a scheduled or scripted skillshare update --all starts failing after upgrading, it is reporting findings that were previously being applied silently. Review them with skillshare audit, then decide whether to pass --force.
skillshare audit # see what is being flagged
skillshare update --all --force # apply anyway, once you have reviewed