Repository navigation

Release Process

Jump to bottom

Brook Li edited this page Oct 16, 2026 · 1 revision

Release Process

Derived from the scripts and CHANGELOG.md.

Chart changes: edit .html-prototype/pack-plugins/echarts/files/, then node skills/ui-pack-maintain/scripts/stamp-chart-plugin.mjs.
Pack changes: bump manifest.version (and schemaVersion only for contract changes), then validate-pack.mjs --pack=<dir> --strict.
Registry: node skills/ui-pack-maintain/scripts/generate-registry.mjs --default-ref=<tag> regenerates .html-prototype/packs/registry.json and the skill's ui/pack-registry.fallback.json. Each pack entry's ref is what install-pack.mjs downloads.
Verify: npm test (fails if either registry is stale at the pinned ref).
Changelog: add a bilingual (English / 中文) section with Added / Changed / Install-update.
Tag the release with the same ref as the registry (e.g. v0.5.3) and publish a GitHub Release so codeload tarballs exist for that tag.

Users update with npx skills add … for both skills, then reinstall packs (install-pack.mjs --pack=<id>).