65 lines
3.1 KiB
Markdown
65 lines
3.1 KiB
Markdown
# ITWorx ModelForge v1.1.0
|
|
|
|
v1.1.0 is a backward-compatible MINOR release. It adds a first-class operator capability, new API
|
|
surface, a new Console workflow and the additive schema migration `20260827_0021` →
|
|
`20260828_0022`; it does not break agent protocol 1 or capability-first application bindings.
|
|
|
|
## Highlights
|
|
|
|
### Audited Node Decommission
|
|
|
|
- Dry-run preview names the exact node, typed blockers, dependencies, cleanup and retained history.
|
|
- Execute is operator-only, transactional, generation/digest guarded and idempotent.
|
|
- Active credentials are revoked; current telemetry, scheduler and disposable inventory truth are
|
|
removed; the node remains as a terminal tombstone.
|
|
- Old credentials receive 401, old persisted identities cannot ordinarily re-enrol, and the
|
|
scheduler excludes terminal nodes.
|
|
- Historical deployments, jobs, probes, capacity/provenance and exactly one
|
|
`NODE_DECOMMISSIONED` audit event remain available.
|
|
|
|
### Console and API reliability
|
|
|
|
- Shared design tokens, light/dark theme persistence, grouped navigation, page-specific headers and
|
|
a mobile drawer.
|
|
- Keyboard-visible focus, accessible navigation and explicit failure/recovery styling.
|
|
- Typed API error envelopes and correlation IDs survive client handling; successful empty responses
|
|
no longer fail JSON decoding.
|
|
|
|
### Packaging and database
|
|
|
|
- Production Node Agent deployments can pin `modelforge-node-agent:1.1.0` or an immutable digest;
|
|
local builds remain possible and no `latest` fallback is used.
|
|
- All published images use digest-pinned Alpine bases, apply signed package security updates and
|
|
run as their dedicated non-root runtime users. Python build tooling is removed after dependency
|
|
consistency verification.
|
|
- Fresh installs migrate an empty supported PostgreSQL database through the full chain to
|
|
`20260828_0022`.
|
|
- Direct upgrades from v1.0.0/schema `20260827_0021` require a verified backup and migrate to
|
|
`20260828_0022`. Application-only rollback is not supported after that schema change; restore the
|
|
verified pre-upgrade backup.
|
|
|
|
Eight stale/test node records were manually removed before this capability existed. That SQL is
|
|
historical evidence, not a supported workflow; v1.1.0 replaces it with the audited API and Console
|
|
operation.
|
|
|
|
## Compatibility
|
|
|
|
| Contract | v1.1.0 |
|
|
| --- | --- |
|
|
| Channel | stable |
|
|
| Runtime schema | `20260828_0022` |
|
|
| Direct upgrade source | v1.0.0 / `20260827_0021` |
|
|
| PostgreSQL | 16+ (17 shipped) |
|
|
| Agent protocol | 1 |
|
|
|
|
SQLite is used by isolated unit tests only and is not a supported production database.
|
|
|
|
## Known limitations
|
|
|
|
- Point-in-time recovery is `NOT_SUPPORTED`; verified snapshot restore is supported.
|
|
- The historical M13/M15 LAB cutover journal remains open because Qdrant external truth is not
|
|
observable. It references no production deployment, active gateway request or scheduler plan.
|
|
- Project-specific Vision, OCR, ASR and ExampleRAG runtime validation remains independently governed
|
|
and is not silently promoted by this release.
|
|
- `VISION_AUTO_ACCEPT_ENABLED=false` remains the ExampleVision production safety setting.
|