Community-registry audit ahead of listing. Upstream 0.4.1 renames the model catalog (private/kimi-k2-6 → private/kimi-k3, drops qwen3-vl-30b) and serves a status page at GET /, so the package was documenting a stale model list and hiding a whole surface. Export that page as a `ui` interface alongside the existing `api` on one host, and unmask the API interface — its URL carries no credentials, so masking hid the address for nothing. PPQ_DATA_DIR stays unset deliberately. With it set, upstream persists a browser-entered key to its own config.json while the StartOS-supplied PPQ_API_KEY still wins at every restart, silently reverting the user. StartOS owns the key via the action; the status page's form renders disabled. CI never ran: build.yml's PR target and tagAndRelease.yml's push trigger both named `master` on a repo whose only branch is `main`. Point them at `main` and reset all three workflows to the package template, dropping the guard job retired in start-technologies@ed0dca2. packageRepo now names the Start9-Community fork, which is where CI runs, where the org's registry variables live, and where releases are cut. Also: drop three .catch handlers on file-model reads, which swallowed a genuine read failure into "no key configured" — readOnce already returns null for a missing file; pass null rather than an empty Mounts for the unmounted subcontainer; inline two single-use interface consts; and rewrite README/instructions against the writing guides, fixing a YAML block that claimed a /data mount the package deliberately does not make.
1.4 KiB
1.4 KiB
Updating the upstream version
Upstream is PayPerQ/ppq-private-mode-proxy,
vendored as the ppq-private-mode-proxy git submodule and built from its own
Dockerfile. The package version tracks upstream's package.json version,
which upstream tags as v<version>.
Determining the upstream version
git -C ppq-private-mode-proxy fetch origin --tags
git -C ppq-private-mode-proxy describe --tags HEAD # current pin
git -C ppq-private-mode-proxy tag --sort=-v:refname | head # latest released
The packaged version lives in startos/versions/current.ts (version: '<upstream>:<revision>').
Applying the bump
- Advance the submodule:
git -C ppq-private-mode-proxy checkout v<version> - Read the upstream diff (
git -C ppq-private-mode-proxy diff <old>..<new>) for anything the package has to follow — new or renamed environment variables, changed endpoints, a changed bind/attestation order (the health check depends on the port being bound only after attestation), or a model catalog change that the docs name. - Update
versioninstartos/versions/current.tsto the new upstreampackage.jsonversion with revision:0(bump only the revision for packaging-only changes), and write release notes in every locale. - Rebuild and test:
make x86(ormake arm), install, verify attestation completes, the Status Page loads, and a/v1/modelsrequest succeeds.