mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-18 18:04:17 +00:00
chore(main): release 0.25.5 (#518)
* chore(main): release 0.25.5 * chore(release): synchronize release metadata * docs(changelog): hand-written 0.25.5 entry --------- 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
0792d0e1a2
commit
91def03e93
@@ -1,3 +1,3 @@
|
||||
{
|
||||
".": "0.25.4"
|
||||
".": "0.25.5"
|
||||
}
|
||||
|
||||
@@ -1,5 +1,34 @@
|
||||
# Changelog
|
||||
|
||||
## [0.25.5] - 2026-10-11
|
||||
|
||||
### New Features
|
||||
|
||||
#### Install
|
||||
|
||||
- **Move installed skills and folders without losing their records** — `skillshare move` moves skills, or whole folders of skills, to another folder of the source and takes the install record with them: the `.metadata.json` entry and accepted audit findings, the project lockfile pin and `config.yaml` group, the project `.gitignore` line and a literal `.skillignore` line. Moving an installed skill by hand left its record behind, so the next `install` or **Install missing** started over. Refs: #510.
|
||||
```bash
|
||||
skillshare move react-best-practices frontend # one skill into frontend/
|
||||
skillshare move pdf docx office # several skills
|
||||
skillshare move frontend archive # a whole folder -> archive/frontend/
|
||||
skillshare move react-best-practices frontend -n # preview
|
||||
```
|
||||
- A move never syncs. It prints `skillshare sync`, which renames the links in your targets. `--dry-run`/`-n` previews, `--json` reports each name with a stable `error_code`, and `-p` works in project mode.
|
||||
- Everything is checked before anything is renamed, and a folder moves whole or not at all. Refused: a skill or folder inside a tracked repo or below a followed source link, a destination inside a skill or a tracked repo, and a short name that matches several skills (use the full path). A target name collision needs `--force`. A target `include`/`exclude` rule that decides differently for the new flat name is warned about; `config.yaml` is not changed.
|
||||
- `install --into` now refuses a folder inside a skill or a tracked checkout, with the same codes.
|
||||
- **`sync` adopts a skill moved by hand** — after a plain `mv`, the next `sync` moves the install record, accepted audit findings and project lock pin to the new path, when exactly one unchanged copy with that name exists. Before, only `install` or **Install missing** did, so `update` and `uninstall` could not find the skill after `mv` + `sync`. `sync` never removes a record; `--dry-run` adopts nothing. Refs: #523.
|
||||
|
||||
#### Dashboard
|
||||
|
||||
- **Move to folder** — select skills and choose **Move to folder…**, or open a folder's menu and choose **Move whole folder…**; the skill page has the same entry. The dialog previews the new paths and link names, blocks a folder move when any item is refused and says why, offers **Move anyway** only for a name collision, and ends with **Sync now**.
|
||||
- **Pick an existing folder when installing into a folder** — the *Into folder* field of the install dialog lists the source root and every existing folder with its skill count. **New folder…** opens a step that builds the path and shows the resulting link name before you confirm.
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
#### Config
|
||||
|
||||
- **`config.yaml` keeps its comments** — every command that wrote the config (`target`, `config set`, installing a tracked repo, and the matching dashboard actions) re-encoded the file and dropped its comments. Comments now stay with their key; a comment on a key the command removed moves in front of the next key. `registry.yaml` keeps its comments the same way. Fixes: #525.
|
||||
|
||||
## [0.25.4] - 2026-10-10
|
||||
|
||||
### New Features
|
||||
|
||||
@@ -8,7 +8,7 @@ description: |
|
||||
noninteractive automation, and guidance for the terminal UI.
|
||||
argument-hint: "[command] [target] [--json] [--dry-run] [-p|-g]"
|
||||
metadata:
|
||||
version: v0.25.4
|
||||
version: v0.25.5
|
||||
---
|
||||
|
||||
# Skillshare CLI
|
||||
|
||||
@@ -9,6 +9,35 @@ All notable changes to skillshare are documented here. For the full commit histo
|
||||
|
||||
---
|
||||
|
||||
## [0.25.5] - 2026-10-11
|
||||
|
||||
### New Features
|
||||
|
||||
#### Install
|
||||
|
||||
- **Move installed skills and folders without losing their records** — `skillshare move` moves skills, or whole folders of skills, to another folder of the source and takes the install record with them: the `.metadata.json` entry and accepted audit findings, the project lockfile pin and `config.yaml` group, the project `.gitignore` line and a literal `.skillignore` line. Moving an installed skill by hand left its record behind, so the next `install` or **Install missing** started over. Refs: #510.
|
||||
```bash
|
||||
skillshare move react-best-practices frontend # one skill into frontend/
|
||||
skillshare move pdf docx office # several skills
|
||||
skillshare move frontend archive # a whole folder -> archive/frontend/
|
||||
skillshare move react-best-practices frontend -n # preview
|
||||
```
|
||||
- A move never syncs. It prints `skillshare sync`, which renames the links in your targets. `--dry-run`/`-n` previews, `--json` reports each name with a stable `error_code`, and `-p` works in project mode.
|
||||
- Everything is checked before anything is renamed, and a folder moves whole or not at all. Refused: a skill or folder inside a tracked repo or below a followed source link, a destination inside a skill or a tracked repo, and a short name that matches several skills (use the full path). A target name collision needs `--force`. A target `include`/`exclude` rule that decides differently for the new flat name is warned about; `config.yaml` is not changed.
|
||||
- `install --into` now refuses a folder inside a skill or a tracked checkout, with the same codes.
|
||||
- **`sync` adopts a skill moved by hand** — after a plain `mv`, the next `sync` moves the install record, accepted audit findings and project lock pin to the new path, when exactly one unchanged copy with that name exists. Before, only `install` or **Install missing** did, so `update` and `uninstall` could not find the skill after `mv` + `sync`. `sync` never removes a record; `--dry-run` adopts nothing. Refs: #523.
|
||||
|
||||
#### Dashboard
|
||||
|
||||
- **Move to folder** — select skills and choose **Move to folder…**, or open a folder's menu and choose **Move whole folder…**; the skill page has the same entry. The dialog previews the new paths and link names, blocks a folder move when any item is refused and says why, offers **Move anyway** only for a name collision, and ends with **Sync now**.
|
||||
- **Pick an existing folder when installing into a folder** — the *Into folder* field of the install dialog lists the source root and every existing folder with its skill count. **New folder…** opens a step that builds the path and shows the resulting link name before you confirm.
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
#### Config
|
||||
|
||||
- **`config.yaml` keeps its comments** — every command that wrote the config (`target`, `config set`, installing a tracked repo, and the matching dashboard actions) re-encoded the file and dropped its comments. Comments now stay with their key; a comment on a key the command removed moves in front of the next key. `registry.yaml` keeps its comments the same way. Fixes: #525.
|
||||
|
||||
## [0.25.4] - 2026-10-10
|
||||
|
||||
### New Features
|
||||
|
||||
Reference in New Issue
Block a user