Solo-developer release workflow

Drop in one release, run one command and upload one replacement ZIP.

The local publisher accepts a complete converter bundle, a raw converter package, or a canonical conversion source ZIP. It rebuilds the website from one release record and regenerates every public checksum.

Drop in

Place exactly one complete converter bundle ZIP, versioned Debian package, or complete conversion source ZIP in release-inbox/ .

Publish

Run ./UPDATE_WEBSITE.sh . The publisher validates the artifact type, metadata, version, engine and website before replacing generated files.

Deploy

Upload the complete replacement ZIP generated under dist/ to Hostinger public_html .

Normal update

The complete command sequence.

cp Sentinel_Linux_Converter_v1_0_18_9.zip release-inbox/
./UPDATE_WEBSITE.sh
cd dist
sha256sum -c *_REPLACEMENT.zip.sha256

Automatically rebuilt

Download, Install, Verify, Status, Releases, Blog feature, Known Issues, Validation, Audit, JSON records, mirrors and site-wide SHA256SUMS .

Automatically checked

Artifact structure, metadata, package or ZIP integrity, engine validation, shell syntax, private-key leakage, JSON, links and checksums.

Automatically backed up

The previous complete public_html is stored under release-backups/ before replacement.

Signing boundary: the publisher can copy a supplied detached signature but never stores a private key or claims a signature exists when it does not.