v0.26.1

skillshare v0.26.1 Release Notes

TL;DR

1. The dashboard remembers findings you accepted. Updating a tracked repo from the dashboard no longer blocks again on findings you already accepted, and Force Retry records the ones it lets through, like update --force in the CLI.
2. Agents update from the dashboard. The Agents Updates tab and an agent's page inside a tracked repo now update agents instead of failing.
3. Tracking guidance matches what install accepts. The built-in skill and install --help no longer suggest --track --all, which install rejects.

Fixed: dashboard updates ignore accepted findings

When an update overrides the audit gate, the findings you accept are recorded in .metadata.json under audit_accepted, so later updates do not block on them again. The CLI did this, and so did dashboard updates of regular skills, but dashboard updates of a tracked repo neither read nor wrote these records. A repo you had force-updated in the CLI was blocked again by the dashboard, and every dashboard Force Retry had to be repeated on the next update.

• Dashboard updates of a tracked repo now skip findings accepted through skillshare update --force, the update prompt or the dashboard.
• Force Retry records the findings it lets through.
• A finding is matched by rule, file and matched text, not by line number. A new finding, or the same rule matching different text, still blocks.
• For an agent repo in a subfolder, acceptances are stored in the agents source, where the CLI keeps them.

Thanks to @483218131 for reporting it (#599).

Fixed: agents cannot be updated from the dashboard

• The Updates tab on the Agents page sent agent names to an endpoint that looked them up as skills, so every agent update there failed, including Force Retry. It now updates agents.
• On the page of an agent inside a tracked repo, Update failed with agent not found. It now updates the repo.
• Prune on an agent deleted upstream now removes that agent; before, it targeted a skill of the same name.
• An agent in a subfolder, or one whose name differs from its file name, is shown as up to date after it updates.

See #600 and #601.

Fixed: tracking guidance suggests a rejected combination

The built-in skill recommended install --track --all, which install rejects. The skill, install --help and plugin --help now show workflows that work:

skillshare install owner/repo --track --name team -g --dry-run   # preview, then run without --dry-run
skillshare check _team -g --json                                  # check upstream changes
skillshare update _team -g && skillshare sync -g                  # update the source, then sync targets

• install --help lists the flags --track cannot be combined with: --all, --yes, --skill and --agent.
• plugin --help shows the discover, add, inspect, check and update workflow for native plugins, which do not use install --track.

Thanks to @salmonumbrella (#596).

Contributors

@483218131, @salmonumbrella, @star-nebula