Plug-in Library: the catalog validator checks every remote release URL in full

scripts/validate.sh now refuses any release URL other than a local file:// path that isn't a release asset (https://github.com/<owner>/<repo>/releases/download/<tag>/<file> with no query, fragment, backslash, or empty, . or .. segment), for packages without a repo too, as Install and Preview do. docs/plugins.md says the release URL rules don't apply to file:// releases from a local catalog.
This commit is contained in:
dotCooCoo committed 2026-11-06 00:32:31 -08:00
1 parent 400187f9d9
commit cc90ad0c3b
2 files changed
+24 -8

No files matched your search

+3 -1
View File
@@ -378,7 +378,9 @@ package can't read files, open the network or crash the app.
(`https://github.com/<owner>/<repo>/releases/download/…`). When the package names a `repo`, the
asset must be in that repository. A `repo` that isn't `https://github.com/<owner>/<repo>` (with
an optional trailing `/` or `.git`) or a folder in one (`https://github.com/<owner>/<repo>/tree/<ref>/…`)
makes Install and Preview refuse every release of the package. A catalog other than the community one is read only when
makes Install and Preview refuse every `https://` release of the package. These rules don't apply
to a release whose `url` is a local `file://` path, which only a local catalog may name (to test
an entry before its release is published). A catalog other than the community one is read only when
`library.refresh {catalog}` names it: an `index.json` on GitHub's hosts over `https://`, or a
local `file://` path.
* **Where it goes.** `<Plug-ins>/Library/<id>/<version>/<id>.wasm` (the `Plug-ins` folder next to