dsh-nvchecker
hougelangley/dsh-nvchecker
用 nvchecker 检查上游发布,报告落后于上游的配方。从 ABBS 风格的配方树重新生成 nvchecker.toml,跑 nvchecker,把上游 tag 逐条与配方的 VER 行比对,产出 Markdown 报告。不改任何配方——升版本始终由人决定,因为 nvchecker 的 use_max_tag 按字面排序,在 2.8.15 与 20160726 混排的仓库上会选错年份 tag。为 AOSC OS loongarch64 第三方树而写,读取标准 ABBS 布局(section/pkg/spec 含 VER= 行)。
安装
dsh plugin --profile web add github:hougelangley/dsh-nvcheckerREADME
dsh-nvchecker
Host plugin for DeepSeek Harness that checks upstream releases with nvchecker and reports recipes that are behind.
Built for the AOSC OS loongarch64 third-party package tree
(HougeLangley/aosc-loongarch64-thirdparty),
but the recipe layout it reads is the plain ABBS one: <section>/<pkg>/spec with a VER= line.
What it does
- Regenerates
nvchecker.tomlfrom the recipe specs. - Runs
nvcheckerand reads the JSON log stream (fd 2). - Diffs each upstream version against the recipe's
VER. - Writes a Markdown report, by default to
~/build/logs/updates.md.
It never edits a recipe. Bumping versions stays a human decision, because nvchecker's
use_max_tag sorts tags lexically and mis-picks year-style tags on repositories that mix
2.8.15 with 20160726 — see Known Limitations.
Config
| Field | Type | Default | Meaning |
|---|---|---|---|
treeRoot | string, required | — | Recipe tree, e.g. ~/build/tree/aosc-loongarch64-thirdparty/packages |
nvcheckerBin | string | nvchecker | nvchecker executable |
checkIntervalHours | number | 24 | Hours between checks; 0 disables the timer and runs once at activation |
reportPath | string | ~/build/logs/updates.md | Report destination |
One check runs at activation; the timer then repeats it.
Prerequisites
nvcheckeronPATH(pip install nvchecker).- The generator script
nvchecker-gen.pyin<treeRoot>/../../../scripts/, and the recipe tree at the layout described above. Generate it once with the generator if it is missing.
Install
plugin_manager install_bundle target=<absolute path to this directory>
Requirements the plugin must meet
Config implements Standard Schema, not a plain object. Cordis calls
Config["~standard"].validate(config) before apply; a plain JSON Schema or a
schemastery schema has no ~standard property, and activation fails with
Cannot read properties of undefined (reading 'validate') even though the
plugin's own code never throws.
nvchecker is resolved by absolute path. pip install --user puts it under
~/.local/bin, which is not on the Harness process PATH. Do not set
nvcheckerBin in the bundle patch: an explicit value there overrides the
absolute-path default and silently yields a report with 0 recipes checked and no
error message.
Known Limitations and Deferred Work
- Auto-bump is intentionally absent.
use_max_tagmis-picks year-style tags: onpyenvit returns20160726instead of2.8.15; onhelm-docsit returns19.0614instead of1.14.2. Two of three reported "updates" were wrong in the first field run. - Sub-path tag prefixes are not handled. A recipe whose
SRCSusestags/kustomize/v$VERreportsv3.3.1rather than5.8.3. Resolving this needs a custom nvchecker source. - Non-numeric upstream tags are skipped, not guessed. The report lists them separately.
- No UI. The plugin is Host-only and writes a file; it does not add a page or panel.