mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-18 18:04:17 +00:00
chore(main): release 0.30.12 (#950)
* chore(main): release 0.30.12 * chore(release): synchronize release metadata * docs(changelog): describe 0.30.12 for users Turn the generated entries into the user-facing notes the changelog keeps, with the --scan example and what each fix changes. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Willie <egg358358@gmail.com>
This commit is contained in:
co-authored by
Willie
parent
52744e2f34
commit
6c40433b47
@@ -1,3 +1,3 @@
|
||||
{
|
||||
".": "0.30.11"
|
||||
".": "0.30.12"
|
||||
}
|
||||
|
||||
@@ -1,5 +1,21 @@
|
||||
# Changelog
|
||||
|
||||
## [0.30.12] - 2026-11-18
|
||||
|
||||
### New Features
|
||||
|
||||
- **Register every Git checkout in a workspace with `--scan`** — some tools, such as Codex, look for project skills only up to the Git root of the folder you open, so skills synced to a workspace folder were not seen inside the checkouts and worktrees it holds. `skillshare project add <root> --scan DIR` now registers the root and each Git checkout found below the scan folders as ordinary project entries with the same settings, in one write. It only adds: a checkout already registered with the same settings is kept, and one with different settings, its own `.skillshare/`, or a name that is already used is skipped with the reason, so it is safe to rerun after a new clone. On a name clash the name comes from the path (`.worktrees/app-a` → `worktrees-app-a`) and is saved. A scan folder that is missing or cannot be read is skipped with a warning. In the dashboard, **Add project** has **Also add each checkout inside this folder**, and **Review** lists each folder as Added, Kept or Skipped before anything is written. See [`project`](https://skillshare.runkids.cc/docs/reference/commands/project#scan). Thanks to @amphetamlne for the request. Refs: #953, #958.
|
||||
```bash
|
||||
skillshare project add ~/work/suite --scan . --scan .worktrees \
|
||||
--target codex --skills-include 'team-*' --dry-run
|
||||
```
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
- **Removing a project says where its MCP and hook settings went** — a removed project's `mcp.projects` and `hooks.projects` entries stay on purpose, but the CLI only warned that `mcp.projects` still contained the root, with no next step. The warning now names the settings and where to remove them, and the dashboard's remove dialog says they stay and that removing the leftover row deletes them. Refs: #955.
|
||||
- **MCP server rows show each Agent once** — rows drew the same Agent logos twice, in the count button and as chips under the name. Only the count button remains; opening it shows the toggles with each Agent's name. Target pickers on MCP and plugin rows fold open and closed and stay still under reduced motion, and a project's MCP **Targets** reads like the global defaults, with **Back to global** behind a confirm. Refs: #952.
|
||||
- **Removing an OMP plugin no longer fails its own preview** — with other OMP plugins registered, apply could reject the removal with "plugin state changed since preview", because their package files were read in a different order each time. Refs: #949.
|
||||
|
||||
## [0.30.11] - 2026-11-17
|
||||
|
||||
### New Features
|
||||
|
||||
@@ -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.11"; // x-release-please-version
|
||||
export const VERSION = "0.30.12"; // x-release-please-version
|
||||
|
||||
@@ -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.11"; // x-release-please-version
|
||||
export const VERSION = "0.30.12"; // x-release-please-version
|
||||
|
||||
@@ -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.11
|
||||
version: v0.30.12
|
||||
---
|
||||
|
||||
# Skillshare CLI
|
||||
|
||||
@@ -9,6 +9,22 @@ All notable changes to skillshare are documented here. For the full commit histo
|
||||
|
||||
---
|
||||
|
||||
## [0.30.12] - 2026-11-18
|
||||
|
||||
### New Features
|
||||
|
||||
- **Register every Git checkout in a workspace with `--scan`** — some tools, such as Codex, look for project skills only up to the Git root of the folder you open, so skills synced to a workspace folder were not seen inside the checkouts and worktrees it holds. `skillshare project add <root> --scan DIR` now registers the root and each Git checkout found below the scan folders as ordinary project entries with the same settings, in one write. It only adds: a checkout already registered with the same settings is kept, and one with different settings, its own `.skillshare/`, or a name that is already used is skipped with the reason, so it is safe to rerun after a new clone. On a name clash the name comes from the path (`.worktrees/app-a` → `worktrees-app-a`) and is saved. A scan folder that is missing or cannot be read is skipped with a warning. In the dashboard, **Add project** has **Also add each checkout inside this folder**, and **Review** lists each folder as Added, Kept or Skipped before anything is written. See [`project`](https://skillshare.runkids.cc/docs/reference/commands/project#scan). Thanks to @amphetamlne for the request. Refs: #953, #958.
|
||||
```bash
|
||||
skillshare project add ~/work/suite --scan . --scan .worktrees \
|
||||
--target codex --skills-include 'team-*' --dry-run
|
||||
```
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
- **Removing a project says where its MCP and hook settings went** — a removed project's `mcp.projects` and `hooks.projects` entries stay on purpose, but the CLI only warned that `mcp.projects` still contained the root, with no next step. The warning now names the settings and where to remove them, and the dashboard's remove dialog says they stay and that removing the leftover row deletes them. Refs: #955.
|
||||
- **MCP server rows show each Agent once** — rows drew the same Agent logos twice, in the count button and as chips under the name. Only the count button remains; opening it shows the toggles with each Agent's name. Target pickers on MCP and plugin rows fold open and closed and stay still under reduced motion, and a project's MCP **Targets** reads like the global defaults, with **Back to global** behind a confirm. Refs: #952.
|
||||
- **Removing an OMP plugin no longer fails its own preview** — with other OMP plugins registered, apply could reject the removal with "plugin state changed since preview", because their package files were read in a different order each time. Refs: #949.
|
||||
|
||||
## [0.30.11] - 2026-11-17
|
||||
|
||||
### New Features
|
||||
|
||||
Reference in New Issue
Block a user