bump upstream to 0.4.1, add the status page UI, fix CI branch triggers
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.
This commit is contained in:
17 files changed
+204
-168
No files matched your search
+15
-9
@@ -2,14 +2,15 @@
|
||||
|
||||
Upstream is [PayPerQ/ppq-private-mode-proxy](https://github.com/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.
|
||||
`Dockerfile`. The package version tracks upstream's `package.json` version,
|
||||
which upstream tags as `v<version>`.
|
||||
|
||||
## Determining the upstream version
|
||||
|
||||
```bash
|
||||
git -C ppq-private-mode-proxy fetch origin
|
||||
git -C ppq-private-mode-proxy log --oneline HEAD..origin/main # anything new?
|
||||
jq -r .version ppq-private-mode-proxy/package.json # current pin
|
||||
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:
|
||||
@@ -17,9 +18,14 @@ The packaged version lives in `startos/versions/current.ts` (`version:
|
||||
|
||||
## Applying the bump
|
||||
|
||||
1. Advance the submodule: `git -C ppq-private-mode-proxy checkout origin/main`
|
||||
2. Update `version` in `startos/versions/current.ts` to the new upstream
|
||||
1. Advance the submodule: `git -C ppq-private-mode-proxy checkout v<version>`
|
||||
2. 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.
|
||||
3. Update `version` in `startos/versions/current.ts` to the new upstream
|
||||
`package.json` version with revision `:0` (bump only the revision for
|
||||
packaging-only changes), and write release notes.
|
||||
3. Rebuild and test: `make x86` (or `make arm`), install, verify attestation
|
||||
completes and a `/v1/models` request succeeds.
|
||||
packaging-only changes), and write release notes in every locale.
|
||||
4. Rebuild and test: `make x86` (or `make arm`), install, verify attestation
|
||||
completes, the Status Page loads, and a `/v1/models` request succeeds.
|
||||
Reference in new issue
Block a user