Signed update feed for Sinty OS, served at updates.sinty.dev. updated polls the
manifest, verifies root -> signing-cert -> manifest, and pulls artifacts from the matching
GitHub Release through the restricted streaming proxy. Signatures are the trust, not the
host; private keys never live here.
PRODUCT_VERSION=26 PRODUCT_BUILD=26A011 \
AMD_FIRMWARE_VERITY_HASH=<hash> NVIDIA_FIRMWARE_VERITY_HASH=<hash> \
./publish.sh <version> <rootfs.erofs> <kernelcache.efi>
Keep firmware-active-{amd,nvidia}.{img,hash} in the same directory as
<rootfs.erofs>. Then upload the eight listed artifacts to the <version> GitHub
Release and push.
The Worker route at /artifacts/<version>/<asset> follows the GitHub Release redirect on
behalf of clients that require a direct 200 response. It accepts only the fixed OTA asset
names and streams response bodies without buffering them.
node --test test/worker.test.mjs
wrangler deploy --dry-run
Maintainers may use generative AI tools as assistants while working on sinty-updates. Non-trivial assisted commits disclose the tool, model, and scope of the work.
AI tools may assist with code comments, documentation, repetitive code, and issue triage. Maintainers make project decisions and review every assisted change before it is merged.
Use these trailers for non-trivial assisted commits:
Assisted-by: <tool>:<model-version>
AI-Scope: <what the tool generated and the prompt or a short prompt summary>
Single-line completions, renames, and formatting changes do not need trailers.
Coding agents must also follow AGENTS.md before changing files, creating commits, or opening pull requests.