diff --git a/COMPATIBILITY.md b/COMPATIBILITY.md index dd28280a304..fdde9e0f81f 100644 --- a/COMPATIBILITY.md +++ b/COMPATIBILITY.md @@ -1,8 +1,8 @@ # Compatibility Contract -## Server v1.6.531 source candidate, not published +## Current release: Server v1.6.531 published -This candidate packages immutable Engine `v0.183.348` and Web Console `1.6.186`. +This release packages immutable Engine `v0.183.348` and Web Console `1.6.186`. The shared Default uses the configured public Native project template; catalog reload also repairs its empty binding when the template is already installed. Existing bindings, custom settings and other projects are preserved. Definitions @@ -12,12 +12,30 @@ driver records, IDs, initialization or action targets. Catalog localization and intentional empty display names are preserved. The personal API Key page, owner RBAC, role schemas, HTTPS, MFA and provider/backend behavior are unchanged. -Fourteen focused Engine and four rendered Web cases passed. Both component -releases passed immutable anonymous readback; this does not establish Server -publication, fresh-install/first-host readiness or driver initialization/restart -acceptance. Server packaging, publication and native acceptance are pending. -Installation examples retain an existing released tag until those gates pass. -See the [candidate note](docs/releases/server-1.6.531.md). +The immutable published producer is `aea01351c270133607bcc0104236c58ff91fc7fd`. +Official Server publication and immutable readback are complete. The registry +manifest for `ghcr.io/pasturestack/server:v1.6.531` is +`sha256:950a9cee2400c3ac0a97aac75e5ff278994d03293e28ac7c821b782e8bed48a4`. +Installation examples use the released numeric `v1.6.531` tag; documentation +commits do not replace the published producer or image. + +Fourteen focused Engine and four rendered Web cases passed, and both component +releases passed immutable readback. The isolated upgrade from Server 530 +repaired an existing unbound Default and introduced no duplicate stacks, services +or drivers after restart. A fresh three-volume installation registered one host +through the public workflow: Default bound to template `1pt1`, with four core +stacks and six active, healthy services. Metadata, managed DNS, HTTPS egress +HTTP 200 and published host port `18297` to probe port `18080` passed. Readiness +survived Server restart, Docker restart, guest reboot with a changed boot ID, +and native API probe recreation from `1i15` to `1i16`. + +Native Chrome 154.0.8037.98 confirmed eleven distinct driver IDs/names on v1 and +v2-beta, zh-tw/en-us at 1440px/390px, four generic icons without duplicate +records, and the same identities after restart. Page errors were zero, and all +five screenshots were visually reviewed. The published deployment and its +subsequent restart also passed. Narrow affected-path acceptance completed with +the existing host defaults and unchanged role logic; broader role/backend +matrices are outside this verification. See the [release note](docs/releases/server-1.6.531.md). ## Server v1.6.529 published diff --git a/README.md b/README.md index 629a6b1f563..7960442cb91 100644 --- a/README.md +++ b/README.md @@ -13,29 +13,35 @@ upstream history, authorship, licenses, and notices. ## Current release -Server [`v1.6.529`](https://github.com/PastureStack/server/releases/tag/v1.6.529) -packages Web Console `1.6.184` and Orchestration Engine `v0.183.347`. +Server [`v1.6.531`](https://github.com/PastureStack/server/releases/tag/v1.6.531) +packages Web Console `1.6.186` and Orchestration Engine `v0.183.348`. +The shared Default uses the configured public Native project template, with +system-stack definitions available before host registration and service +activation triggered by the first active host. Machine driver cards display +each driver's API name, including drivers sharing the generic icon; catalog +names retain localization and formatting. Personal API Keys are available +without an accessible environment. + API Key permissions follow the actual operation and the owner's live authority. Authorized compose exports and registered actions can load their exact target without granting ordinary read/list access or broader resource scope. Stack-scoped Container and Instance Link queries retain live ancestry checks and work with MariaDB's default optimizer, including nullable Stack references. -API Key subscriptions retain their first terminal close/failure outcome and -bounded audit delivery retry without restoring authorization. The console labels -event subscriptions even when a completion record has no target ID; no resource -picker or grant capability is added. Official publication and immutable readback -passed. Thirty-six focused subscription cases passed with two local-MFA accounts -per tested role, including live revocation and separate handshake/terminal audit. -This is not acceptance of every resource or operation in the permission matrix. +Subscription audit retains the first terminal close/failure outcome and bounded +delivery retry without restoring authorization. +The console labels event subscriptions even when a completion record has no +target ID; resource-picker and grant capabilities retain their existing boundaries. Registration tokens use dedicated Basic authentication. Native project creation preserves the creator's initial membership and default networks. HA database exports return a SQL ZIP only after successful, nonempty output; failures clean up temporary files without returning command stderr or secrets. -See the [release note](docs/releases/server-1.6.529.md) for component identities +See the [release note](docs/releases/server-1.6.531.md) for component identities and acceptance limits. +Narrow affected-path acceptance completed; see the release note for its scope. + The console supports OIDC, TOTP and passkeys, role-aware resource operations, container resource/hardware settings, and movable terminal/log windows. Hardware options require compatible node software and actual host capabilities; @@ -76,7 +82,7 @@ docker run -d --name pasturestack-server --restart unless-stopped -p 8080:8080 \ -v pasturestack-cattle:/var/lib/cattle \ -v pasturestack-mysql:/var/lib/mysql \ -v pasturestack-mysqllog:/var/log/mysql \ - ghcr.io/pasturestack/server:v1.6.529 + ghcr.io/pasturestack/server:v1.6.531 ``` For HTTPS termination at a reverse proxy, set the exact public origin: @@ -84,7 +90,7 @@ For HTTPS termination at a reverse proxy, set the exact public origin: ```yaml services: pasturestack-server: - image: ghcr.io/pasturestack/server:v1.6.529 + image: ghcr.io/pasturestack/server:v1.6.531 restart: unless-stopped ports: - "8080:8080" diff --git a/docs/releases/server-1.6.531.md b/docs/releases/server-1.6.531.md index b73625c6874..69e7b63e0ca 100644 --- a/docs/releases/server-1.6.531.md +++ b/docs/releases/server-1.6.531.md @@ -1,6 +1,11 @@ # Server v1.6.531 本版組裝已正式不可變發行的 Engine `v0.183.348` 與 Web Console `1.6.186`。 +Server 數字 tag `v1.6.531` 已正式發布並完成不可變成品讀回，producer source 為 +`aea01351c270133607bcc0104236c58ff91fc7fd`； +`ghcr.io/pasturestack/server:v1.6.531` 的 registry manifest 為 +`sha256:950a9cee2400c3ac0a97aac75e5ff278994d03293e28ac7c821b782e8bed48a4`。 +文件更新不替換此正式 source 或映像身分。 Engine 的預設專案範本名稱對齊真正 Catalog `project.yml` 的 `PastureStack Native`。乾淨安裝的共用 Default 能自動綁定範本； @@ -12,7 +17,7 @@ catalog reload 也可補上已安裝範本、但 `adminProject` 仍未綁定的 零主機時可先有 network-services、IPsec、scheduler 與 healthcheck 定義， 服務啟動沿用首台 active host 的正常觸發。Network、Metadata、DNS 與 health -實際就緒仍須完成首台主機原生驗收，不能以 API 啟動或空容器清單宣告成功。 +本版隔離首台主機原生驗收已確認實際就緒。 Web 的原共用 driver card 在模型沒有 `catalogDisplayName` 時顯示 native API 名稱，讓共用通用圖示的 `hyperv`、`libvirt`、`vmwarefusion`、`virtualbox` @@ -41,8 +46,7 @@ vendor-pending exact-set、原必要 gates 與既有元件歷史負控制不弱 ## 待 vendor 的安全範圍 -正式發布 run `38507013620` 在 merged-rootfs 安全 exact-set gate 停止， -尚未發布 Server 映像。該次 Trivy 原始掃描新增 6 個 PCRE2 CVE， +本版安全 tracker 收錄 Trivy 原始掃描新增的 6 個 PCRE2 CVE， 各對應 Ubuntu 26.04 `libpcre2-8-0` 與 `libpcre2-posix3` 的 `10.46-1build1`，合計 12 筆 MEDIUM，`FixedVersion` 均為空。 vendor-pending 現記錄共 10 個 CVE／20 筆精確 MEDIUM package findings， @@ -67,13 +71,32 @@ tracker 的 `needs-evaluation` 沿用本專案的到期覆核狀態， `verifiedAt` 保留此次官方讀回。這些 finding 仍待 vendor，未宣告已修復、 未改成 VEX not-affected 或安全豁免。允許 severity、空 `FixedVersion`、 精確 package/CVE/version/target 比對與原發布 gates 保持原契約； -正式 pipeline 仍須用最新掃描重新通過安全與發布驗證。 +正式 Server 發布與不可變讀回已完成；待 vendor 清單仍依原 exact-set 契約覆核。 發行流程保留原來源／封裝、安全／SBOM、CodeQL、不可變發行及成品讀回閘門。 -部署驗收涵蓋零主機／首台主機 readiness、driver 初始化／重啟識別； -上述元件測試不等於完整角色／資源矩陣通過。安裝及元件配對見 Server README， +安裝及元件配對見 Server README， 正式映像身分與安全掃描結果由同版本 GitHub Release 提供。 +## 受影響路徑原生驗收 + +現有 Server 530 未綁定 Default 的升級補綁與一輪重啟通過，沒有新增重複 +stack、service 或 driver。Fresh Server 531 使用三個持久化 volumes，經正常 +公開流程註冊一次首台主機；Default 綁定範本 `1pt1`，四個 core stacks 與六個 +core services 均 active／healthy。Metadata、managed DNS、HTTPS egress HTTP +200，以及公開 host port `18297` 到 probe port `18080` 的存取均通過。 + +隔離 Server restart、Docker restart、guest reboot（boot ID 已改變）後保留 +上述 readiness；再經正常 native API 重建 probe workload，`1i15` 到 `1i16` +仍通過。正式發行映像的現有安裝部署與後續 restart 亦已通過。 + +真實 Chrome 154.0.8037.98 載入 Server 531／Web 186：十一個不同 driver ID 與 +名稱在 v1／v2-beta exact-set 相符，zh-tw／en-us 的 1440px／390px 都顯示正確。 +四個 generic icons 對應不同記錄；重啟後 IDs／names 不變，page errors 為零， +五張截圖均已人工檢視。沒有刪除或合併 driver。 + +Narrow affected-path acceptance completed。驗收使用既有 host 預設 backend， +role logic 未變；範圍涵蓋上述受影響路徑，不宣稱所有角色／backend 矩陣完成。 + ## 升級與回復 使用完成正式發行與讀回的整套 Server 映像，不在運行容器中替換元件。