ITWorx ModelForge v1.2.2

A security and public-packaging patch over v1.2.1. The API contract and agent protocol remain unchanged. Runtime Worker dependency versions change and therefore require fresh LAB compatibility evidence before promotion; no production capability is changed automatically.

Security

The Runtime Worker now upgrades its digest-pinned Ubuntu base during the image build.
Build-only Linux kernel headers are removed after dependency installation instead of remaining in the running Runtime Worker image.
Explicit shipping-image validation rebuilds all four images without Docker layer cache, refreshes the Node Agent's digest-pinned Python base, upgrades fixed Runtime Worker dependencies, and removes pip/setuptools/wheel after the final dependency check.
Pillow, protobuf, SentencePiece, Sentence Transformers, Transformers and inherited Python security dependencies are pinned to reviewed fixed versions.
The public-candidate acceptance gate builds and scans all four images, binds each Trivy report to its exact image ID and fails on every fixable or newly observed HIGH/CRITICAL vulnerability.
The Node Agent's upstream-unfixed Debian findings are non-blocking only through an exact reviewed CVE/package/version/severity baseline. Any drift requires a new review.
PostgreSQL provisioning revokes the default public temporary-table privilege before granting the separate migration-owner and runtime roles; the runtime startup attestation fails closed if that boundary is weakened.

Reliability

Schema 20260830_0024 now passes PostgreSQL percent syntax through Psycopg without interpreting %rowtype or %I as client placeholders.
Server acceptance supports a sibling Docker daemon without weakening production Compose: the exact bootstrap SQL and reviewed configuration are transferred through the Docker API, and HTTP contracts are probed inside the isolated candidate network.

Compatibility

Contract	v1.2.2
Version	`1.2.2`
Channel	`stable`
Database schema	`20260830_0024`
Agent protocol	`1`, accepts `1`
Minimum direct upgrade	`v1.0.0`
Minimum PostgreSQL major	`16`

Upgrade classification

The control plane and Node Agent change is transparent. The Runtime Worker inference dependency update is behavioral: exact LAB probes, output-shape checks and unload/reclaim evidence are required before an existing runtime profile can be promoted. Embedding-space identities and project indexes are not reused or changed automatically.

Post-publication operational verification

The exact Runtime Worker built from b8755394117affad0178a79a627cf5574d3c8eef passed a fresh GPU Node LAB probe on 2026-09-01, including offline load, finite normalized [1, 1024] output and exact VRAM return to baseline after unload. Production remained on v1.2.1 pending the separate backup, migration and explicit deployment gates. See quality/V1_2_2_LAB_VERIFICATION.md.

Known limitations

Production upgrade from schema 0022 to 0024 requires downtime, a verified recovery point and separate migration-owner/runtime-role provisioning; publication never performs it automatically.
Public pull-request CI remains disabled until an isolated runner can enforce denial of private network egress for untrusted fork code.
ExampleRAG's ModelForge shadow candidate is not promotion-eligible after two critical retrieval regressions; the existing production alias and vector space remain unchanged.
ExampleVision owner-photo and ASR natural-speech qualification still require owner-provided ground truth. Catalog images and synthetic/library audio are not accepted as substitutes.
Point-in-time database recovery remains NOT_SUPPORTED.

3.7 KiB Raw Blame History