diff --git a/.github/release-please-manifest.json b/.github/release-please-manifest.json index 971495c12..46feac121 100644 --- a/.github/release-please-manifest.json +++ b/.github/release-please-manifest.json @@ -1,3 +1,3 @@ { - ".": "0.30.9" + ".": "0.30.10" } diff --git a/CHANGELOG.md b/CHANGELOG.md index 1473a24ef..62d43a16f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,25 @@ # Changelog +## [0.30.10] - 2026-11-17 + +### New Features + +- **Trust the Codex hooks skillshare writes** — Codex runs a user-level hook only after it is trusted, and only `/hooks` in its TUI recorded that. Every hook skillshare added or moved started untrusted, and `codex exec` skipped it without a word. `skillshare hooks sync --trust -g` now asks Codex which of skillshare's hooks are new or changed, in every Codex home it manages (account homes such as `codex-2` included), lists them with their full commands and records trust once you confirm. `--yes` (`-y`) skips the question for scripts; without a terminal and without `--yes`, nothing is trusted and the command fails. `--json` never asks, and reports each hook in a `codexTrust` list as `trusted`, `unchanged` or `needed`. Only `trusted_hash` in `config.toml` changes: a hook that is disabled in Codex is reported, not switched on, and hooks skillshare does not own are never touched. A home Codex cannot list is named in the error while the other homes are still trusted. In the dashboard, the Hooks page has a **Trust Codex hooks** button in global scope once nothing is waiting to be synced; its dialog shows each command and records trust only after you confirm. Global mode only, and `codex` must be on `PATH`; project-level and plugin hooks are not covered. See [`hooks`](https://skillshare.runkids.cc/docs/reference/commands/hooks#codex-trust). Thanks to @salmonumbrella for the request and the implementation. Refs: #828, #829. + ```bash + skillshare hooks sync --trust -g # lists the commands, asks once + skillshare hooks sync --trust --yes -g # no question, for scripts + ``` + +### Bug Fixes + +- **`sync` and `init` leave alone what skillshare did not create** — on Windows, `init` followed by `sync` deleted entries in a tool's skills folder that skillshare never made, with no backup, and re-pointed another tool's junction. The manifest of what skillshare created now decides. Orphan cleanup keeps a folder whose name only looks like skillshare's flat naming (`team__shared`, `_drafts`) and a broken link that the manifest does not record, and warns about them. Merge sync re-points a same-name link only when skillshare made it or it already points into the source; otherwise the entry is reported as kept local. `sync --force` still removes or replaces these. During `init`, a folder identical to the source is moved to the trash under `replaced-by-init/` instead of being deleted. `doctor` reports such entries as kept, and a broken link that `sync` will remove as broken. Thanks to @endgame302 for the report and the fix. Refs: #914. +- **`diff` lists what `sync` removes** — the agent diff, in the CLI and the dashboard, listed every link no agent maps to as a removal, although agent sync prunes a link only in merge mode and only when it is broken or points into the source; a live link to another location was listed forever. The CLI diff also listed no orphan links for merge-mode skills, so a skill removed from the source showed nothing until `sync` pruned its link. Both now list exactly the links `sync` removes. Refs: #939, #940, #942. +- **`init` names the agent files it kept** — when a tool already had a file under an agent's name, the first sync kept it and `init` still said "Synced", while the tool went on loading its own file. `init` now prints a line per tool that names the kept files and the command that replaces them (`skillshare sync agents --force`). In symlink mode it says the whole agents folder was kept. Refs: #938, #943. +- **`sync agents --force` takes over an agent file that already matches** — where agents are copied instead of linked (Windows without Developer Mode), a file a tool already had with the same content as the source was kept and never tracked, even with `--force`, so later changes to the source did not reach it. With `--force` the file is now recorded as skillshare's and later syncs update it. Without `--force` nothing changes. Refs: #944. +- **Updating skills from the dashboard fetches each repository once** — the Updates tab cloned the repository once per skill and reinstalled every one, so 31 skills from 8 repositories took over a minute where `skillshare update --all` takes 16 seconds, and unchanged skills were reported as updated. Skills are now grouped by repository and branch, as the CLI does, and a skill that already matches upstream is shown and counted as up to date. Refs: #931. +- **One progress indicator while an update runs** — an update showed a spinner in the status card, a progress bar, a spinner on the active row and a moving line under it at once, and the bar disappeared before it reached the end. There is now one bar that shows work before the first item finishes and completes before it fades; the active row is marked by a light sweep over its status text. Backup, install from config, the plugin update dialog and pending Doctor checks follow the same rule. Refs: #932. +- **The hooks dialog for targets opens with nothing selected** — the dialog where a hook is edited or removed in its target file opened with every hook ticked, so removing one could import the rest by accident. It now opens with nothing selected, and its entry points are named **Hooks in targets** and **Not managed yet** instead of "Import". The review step lists each hook once, shows a count per action on each file and opens a diff on request. When the OpenCode CLI is missing, the dashboard says the command was not found and what to do, instead of showing the raw error. Refs: #935. + ## [0.30.9] - 2026-11-16 ### New Features diff --git a/herdr/skillshare-mod/mods/skillshare/version.js b/herdr/skillshare-mod/mods/skillshare/version.js index 2dddd51b2..2ed0d6fcb 100644 --- a/herdr/skillshare-mod/mods/skillshare/version.js +++ b/herdr/skillshare-mod/mods/skillshare/version.js @@ -1,3 +1,3 @@ // The skillshare release this panel shipped with. Release Please rewrites it in every release // (.github/release-please-config.json), so the panel can tell when a newer release has one. -export const VERSION = "0.30.9"; // x-release-please-version +export const VERSION = "0.30.10"; // x-release-please-version diff --git a/herdr/skillshare/mods/skillshare/version.js b/herdr/skillshare/mods/skillshare/version.js index 2dddd51b2..2ed0d6fcb 100644 --- a/herdr/skillshare/mods/skillshare/version.js +++ b/herdr/skillshare/mods/skillshare/version.js @@ -1,3 +1,3 @@ // The skillshare release this panel shipped with. Release Please rewrites it in every release // (.github/release-please-config.json), so the panel can tell when a newer release has one. -export const VERSION = "0.30.9"; // x-release-please-version +export const VERSION = "0.30.10"; // x-release-please-version diff --git a/skills/skillshare/SKILL.md b/skills/skillshare/SKILL.md index 9b404255c..283847c01 100644 --- a/skills/skillshare/SKILL.md +++ b/skills/skillshare/SKILL.md @@ -9,7 +9,7 @@ description: | noninteractive automation, and guidance for the terminal UI. argument-hint: "[command] [target] [--json] [--dry-run] [-p|-g]" metadata: - version: v0.30.9 + version: v0.30.10 --- # Skillshare CLI diff --git a/website/src/pages/changelog.md b/website/src/pages/changelog.md index d6ca3561f..2b074cb03 100644 --- a/website/src/pages/changelog.md +++ b/website/src/pages/changelog.md @@ -9,6 +9,26 @@ All notable changes to skillshare are documented here. For the full commit histo --- +## [0.30.10] - 2026-11-17 + +### New Features + +- **Trust the Codex hooks skillshare writes** — Codex runs a user-level hook only after it is trusted, and only `/hooks` in its TUI recorded that. Every hook skillshare added or moved started untrusted, and `codex exec` skipped it without a word. `skillshare hooks sync --trust -g` now asks Codex which of skillshare's hooks are new or changed, in every Codex home it manages (account homes such as `codex-2` included), lists them with their full commands and records trust once you confirm. `--yes` (`-y`) skips the question for scripts; without a terminal and without `--yes`, nothing is trusted and the command fails. `--json` never asks, and reports each hook in a `codexTrust` list as `trusted`, `unchanged` or `needed`. Only `trusted_hash` in `config.toml` changes: a hook that is disabled in Codex is reported, not switched on, and hooks skillshare does not own are never touched. A home Codex cannot list is named in the error while the other homes are still trusted. In the dashboard, the Hooks page has a **Trust Codex hooks** button in global scope once nothing is waiting to be synced; its dialog shows each command and records trust only after you confirm. Global mode only, and `codex` must be on `PATH`; project-level and plugin hooks are not covered. See [`hooks`](https://skillshare.runkids.cc/docs/reference/commands/hooks#codex-trust). Thanks to @salmonumbrella for the request and the implementation. Refs: #828, #829. + ```bash + skillshare hooks sync --trust -g # lists the commands, asks once + skillshare hooks sync --trust --yes -g # no question, for scripts + ``` + +### Bug Fixes + +- **`sync` and `init` leave alone what skillshare did not create** — on Windows, `init` followed by `sync` deleted entries in a tool's skills folder that skillshare never made, with no backup, and re-pointed another tool's junction. The manifest of what skillshare created now decides. Orphan cleanup keeps a folder whose name only looks like skillshare's flat naming (`team__shared`, `_drafts`) and a broken link that the manifest does not record, and warns about them. Merge sync re-points a same-name link only when skillshare made it or it already points into the source; otherwise the entry is reported as kept local. `sync --force` still removes or replaces these. During `init`, a folder identical to the source is moved to the trash under `replaced-by-init/` instead of being deleted. `doctor` reports such entries as kept, and a broken link that `sync` will remove as broken. Thanks to @endgame302 for the report and the fix. Refs: #914. +- **`diff` lists what `sync` removes** — the agent diff, in the CLI and the dashboard, listed every link no agent maps to as a removal, although agent sync prunes a link only in merge mode and only when it is broken or points into the source; a live link to another location was listed forever. The CLI diff also listed no orphan links for merge-mode skills, so a skill removed from the source showed nothing until `sync` pruned its link. Both now list exactly the links `sync` removes. Refs: #939, #940, #942. +- **`init` names the agent files it kept** — when a tool already had a file under an agent's name, the first sync kept it and `init` still said "Synced", while the tool went on loading its own file. `init` now prints a line per tool that names the kept files and the command that replaces them (`skillshare sync agents --force`). In symlink mode it says the whole agents folder was kept. Refs: #938, #943. +- **`sync agents --force` takes over an agent file that already matches** — where agents are copied instead of linked (Windows without Developer Mode), a file a tool already had with the same content as the source was kept and never tracked, even with `--force`, so later changes to the source did not reach it. With `--force` the file is now recorded as skillshare's and later syncs update it. Without `--force` nothing changes. Refs: #944. +- **Updating skills from the dashboard fetches each repository once** — the Updates tab cloned the repository once per skill and reinstalled every one, so 31 skills from 8 repositories took over a minute where `skillshare update --all` takes 16 seconds, and unchanged skills were reported as updated. Skills are now grouped by repository and branch, as the CLI does, and a skill that already matches upstream is shown and counted as up to date. Refs: #931. +- **One progress indicator while an update runs** — an update showed a spinner in the status card, a progress bar, a spinner on the active row and a moving line under it at once, and the bar disappeared before it reached the end. There is now one bar that shows work before the first item finishes and completes before it fades; the active row is marked by a light sweep over its status text. Backup, install from config, the plugin update dialog and pending Doctor checks follow the same rule. Refs: #932. +- **The hooks dialog for targets opens with nothing selected** — the dialog where a hook is edited or removed in its target file opened with every hook ticked, so removing one could import the rest by accident. It now opens with nothing selected, and its entry points are named **Hooks in targets** and **Not managed yet** instead of "Import". The review step lists each hook once, shows a count per action on each file and opens a diff on request. When the OpenCode CLI is missing, the dashboard says the command was not found and what to do, instead of showing the raw error. Refs: #935. + ## [0.30.9] - 2026-11-16 ### New Features