ls-rebuild-release

Rebuild Lite Suite Electron installers and update manifest hashes.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahostbr/liteharness-plugin --skill ls-rebuild-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-rebuild-release
Source: https://github.com/ahostbr/liteharness-plugin/tree/main/skills/ls-rebuild-release
Command: npx skills add https://github.com/ahostbr/liteharness-plugin --skill ls-rebuild-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of keeping Lite Suite installers and litesuite.dev metadata in sync after changes like icon updates, version bumps, or build pipeline adjustments, where manual rebuilding and re-hashing is error-prone.

Core Features & Use Cases

  • Parallel rebuild of app installers: Runs pnpm dist for each Electron desktop app (LiteEditor, LiteSpeak, LiteTerminal, LiteImage) to produce both NSIS installers and portable Win zips.
  • Deterministic portable ZIP integrity updates: Generates SHA-256 hashes and file sizes from the portable .zip artifacts (the inputs the LiteCore installer downloads and extracts).
  • Manifest and GitHub release automation: Updates manifest.json on litesuite.dev with new sha256, size, updatedAt, and download URLs, then recreates GitHub releases using the portable zips as the primary asset.

Quick Start

Rebuild and release the Lite Suite apps by running the ls-rebuild-release instructions after any icon changes or version bumps so the portable ZIPs, hashes, manifest, and GitHub releases are updated together.

Frequently Asked Questions about ls-rebuild-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rebuild Electron installers and update release metadata in one pass?

To rebuild Electron installers and update release metadata, run pnpm dist to rebuild Lite Suite apps, extract SHA-256 hashes and sizes from portable ZIPs, edit manifest.json, and recreate GitHub releases with the ZIP as the primary asset.

What is the best way to automate manifest.json updates after an Electron build?

Automating manifest.json updates requires extracting the SHA-256 hash and file size from the newly built portable ZIP artifacts, then precisely editing the updatedAt, sha256, size, version, and downloadUrl fields to match the new payloads.

How does SHA-256 hashing work for portable ZIP integrity in release automation?

SHA-256 hashing for portable ZIP integrity generates a cryptographic checksum from the final ZIP artifact, allowing the LiteCore installer to verify downloaded payloads against the litesuite.dev manifest entries before extraction.

Do I need pnpm to run dist rebuilds for Lite Suite Electron apps?

Yes, pnpm is required to run dist rebuilds for Lite Suite Electron apps. The rebuild process depends on pnpm-based dist builds to produce both NSIS installers and portable Win ZIPs for LiteEditor, LiteSpeak, LiteTerminal, and LiteImage.

When should I regenerate hashes and manifest entries for GitHub releases?

You should regenerate hashes and manifest entries for GitHub releases after any version changes, icon updates, or build pipeline adjustments that alter the downloaded portable ZIP payloads for the LiteCore installer.

Why does my litesuite.dev manifest show outdated integrity hashes after a version bump?

Your litesuite.dev manifest shows outdated integrity hashes because the portable ZIP artifacts changed during the version bump, requiring a full rebuild to extract new SHA-256 hashes and sizes and update the manifest.json download metadata.