|
2 | 2 |
|
3 | 3 | ## Development |
4 | 4 |
|
5 | | -## Version 0.4.1-rc.4 |
6 | | - |
7 | | -### Changed |
8 | | - |
9 | | -- A hook's own payload file may be binary too, like the rest of a skill body. |
10 | | - |
11 | | -### Fixed |
12 | | - |
13 | | -- A trailing `#` comment is no longer folded into a re-quoted YAML value. |
14 | | -- A `|` block under a list item keeps its literal text; it was being rewritten |
15 | | - as if it were YAML. |
16 | | -- An `mcp.yml` that exists but cannot be read is reported, not skipped in |
17 | | - silence. |
18 | | -- Installing git-lfs and syncing now really fetches the assets; the check was |
19 | | - frozen at the moment the repository was added. |
20 | | -- Clicking a repository's error dot shows the message, not its internal |
21 | | - identifier. |
22 | | -- The editor schema for `mcp.yml` no longer accepts an empty `name` or a blank |
23 | | - `url`, and no longer rejects an unknown top-level key. |
24 | | - |
25 | | -## Version 0.4.1-rc.3 |
26 | | - |
27 | | -### Added |
28 | | - |
29 | | -- Skills may ship binary files. An image, font, or compiled helper is copied, |
30 | | - hashed, and verified like any other file. |
31 | | - |
32 | | -### Fixed |
33 | | - |
34 | | -- One unreadable skill no longer takes every skill after it in the repository |
35 | | - with it. It is skipped alone, and named. |
36 | | -- Cloning a repository that needs Git LFS now fails when git-lfs is missing, |
37 | | - instead of quietly leaving pointer files in place of every asset. |
38 | | - |
39 | | -## Version 0.4.1-rc.2 |
| 5 | +## Version 0.4.1 |
40 | 6 |
|
41 | 7 | ### Added |
42 | 8 |
|
43 | 9 | - Prebuilt arm64 builds for Linux and Windows: desktop bundles, CLI archives, |
44 | 10 | and the one-line installers, alongside the existing x64 and macOS ones. |
45 | 11 | - A JSON Schema for `mcp.yml`, published with every release: point an editor at |
46 | 12 | it for completion, hover documentation, and validation as you type. |
47 | | - |
48 | | -### Changed |
49 | | - |
50 | | -- A bare `{param}` in a header or `env` value is read as a placeholder, not as |
51 | | - the YAML mapping a leading `{` normally opens. |
52 | | - |
53 | | -### Fixed |
54 | | - |
55 | | -- An `mcp.yml` that cannot be parsed now says so in the app's notifications |
56 | | - and on the CLI's standard error, instead of vanishing with its presets. |
57 | | -- A rejected `mcp.yml` names what the parser objected to, not just which |
58 | | - server it gave up on. |
59 | | -- The Windows MSIX now always packages the desktop app; it picked between two |
60 | | - binaries sharing a file name. |
61 | | - |
62 | | -## Version 0.4.1-rc.1 |
| 13 | +- Skills may ship binary files. An image, font, or compiled helper is copied, |
| 14 | + hashed, and verified like any other file. |
63 | 15 |
|
64 | 16 | ### Changed |
65 | 17 |
|
66 | 18 | - A skill with extra or oddly typed frontmatter fields installs instead of |
67 | | - being dropped: `version: 1.0` and `executables: run.sh` now read as intended. |
68 | | -- A one-line `description:` may hold a second colon, as prose often does. It |
69 | | - used to be read as a nested mapping and rejected the skill. |
| 19 | + being dropped: only `name` is required. |
| 20 | +- A one-line `description:` may hold a second colon, and a header or `env` |
| 21 | + value may be a bare `{param}`. |
70 | 22 |
|
71 | 23 | ### Fixed |
72 | 24 |
|
73 | 25 | - "Invalid YAML frontmatter" now says what is wrong and on which line of the |
74 | 26 | file, instead of naming only the file. |
| 27 | +- An `mcp.yml` that cannot be read or parsed says so, in the app's |
| 28 | + notifications and on the CLI's standard error. |
| 29 | +- One unreadable skill no longer takes every skill after it in the repository |
| 30 | + with it. It is skipped alone, and named. |
75 | 31 | - Switching a repository's branch refreshes its skills and MCP servers, instead |
76 | | - of leaving the Skills and MCP pages on the previous branch's contents. |
| 32 | + of leaving both pages on the previous branch's contents. |
77 | 33 | - Syncing a repository refreshes the MCP catalog too, which it had left to the |
78 | 34 | next visit to an MCP page. |
| 35 | +- Cloning a repository that needs Git LFS fails when git-lfs is missing, |
| 36 | + instead of quietly leaving pointer files in place. |
| 37 | +- The Windows MSIX packages the desktop app; it used to pick between two |
| 38 | + binaries sharing a file name. |
79 | 39 |
|
80 | 40 | ## Version 0.4.0 |
81 | 41 |
|
|
0 commit comments