Server assembles the control platform, orchestration engine, web console, node agent, authentication service, proxy, catalog, and database into a deployable image. PastureStack is an independent community effort to preserve, audit, and modernize the Rancher 1.6 ecosystem. It is not affiliated with or endorsed by Rancher Labs or SUSE.
Upstream: rancher/rancher. This fork
preserves upstream history, authorship, dates, tags, licenses, and copyright
notices. PastureStack maintenance is consolidated after the preserved upstream
boundary.
Server v1.6.516 已正式發布，封裝 Web Console 1.6.178，修正停用環境因不適用的
網路／政策 API 請求而無法載入詳細資料的問題。
表單以 13 個語系說明網路設定暫不可用；全域環境／成員權限、其他狀態的錯誤處理及
既有日誌／終端修正保持，正式 Web CI 848／848 通過。
內建 Catalog 包含 IPsec Overlay 第 12 版與已發布的 runtime v0.14.38，不會自動升級
既有堆疊，使用者覆寫與 plugin 分工不變。
正式映像與公開工件讀回已通過；隔離 QA 首次啟動／重啟各經 10 次有界探測後取得
HTTP 200／pong，runtime 設定與五項核心表筆數差異為 0，既有 AppArmor、三個 named
volumes 與 unless-stopped 保留。Docker health 為 null，不宣稱 healthy，也未部署公司站。
單一停用環境的詳細資料／重載／取消與原生刪除、列表重載後消失已觀察；parent 收尾
timeout 的 HOLD 保留。獨立唯讀資料庫觀察確認該環境與四個網路已清除、成員與相依資源為空；
但未完成新 API／完整外部資料保留驗證，不宣稱完整原生流程 PASS。完整矩陣 INCOMPLETE。
詳見 v1.6.516 修補與驗收邊界。
本版封裝已發布的 Web Console 1.6.177，修正已結束的日誌／終端工作區重新連線，
以及延後抵達的回應、socket 與 timer 回呼誤更新舊工作區的問題。明確開啟新項目與
仍在執行中的連線可繼續使用；權限、API、工作區保存格式及 MFA 契約不變。
Web 正式 CI 37255121243 通過 841 項測試（新增 17 項），兩份 archive 原 bytes 一致；
數字 lightweight tag 1.6.177 綁定 signed source commit
b9b841e65afe1d89a5b03ac767e9168bccd3c3ea，不是 signed tag；
正常 PR #175 squash merge 5d150806be20226657e5caa8a0150d068006c772 的 tree 相同且簽章已驗證。
匿名 HTTP 200 讀回 archive 2982494 bytes、SHA256
4e34eb2b3165f078134cddcf1721239b3da7baf11dd683991b2d6aa5bae944e0。
Engine 333、Catalog Service 0.20.12、其他元件、plugins、460 base 與單 runtime layer 流程不變。
Server 515 正式 source 為 f0267ff3a347ea526088db1749b1d3c8dfd9bd37，不可變映像為
ghcr.io/pasturestack/server:v1.6.515@sha256:fcc79f616927040ef2b3a5c58662fa948823220dbc57ffe275dee2ad88764d47。
正式 publisher 37256753740
及獨立公開成品／runtime／security 讀回通過。
隔離測試站已升級 Server 515 / Web 177，獨立部署讀回通過：首次啟動第 10 次、
重啟第 11 次探測取得 HTTP 200/pong；runtime 設定、環境覆寫、三個具名資料卷
與五張核心表筆數保持不變，docker-default、unless-stopped 及 514 回滾映像與備份保留。
映像沒有 Docker Healthcheck；running/pong 不等於 Docker healthy，也不是原生生命週期 PASS。
Quick Start 對齊已發布 515；514 原映像、設定、資料卷與備份保留供 rollback。
最新一輪 Project v2 原生驗收仍為 HOLD：停用請求回 HTTP 200 後，介面等待逾時；
原生移除與資料庫清理尚未完成。本版完整原生驗收仍待完成，全矩陣仍 INCOMPLETE，
歷史 HOLD 不提升。
詳見 本版發行事實與驗收邊界。
本版封裝 Catalog Service 0.20.12：Git .git 中繼資料不再被誤建成空範本，
同一來源 commit 已有空索引時會透過原有交易重建該 Catalog，而非跳過修復。
Web Console 1.6.176 同時修正升級 Ember 後原生選單的 mut 綁定：
選取成員角色時必須真正更新模型，並檢查相同寫法的 21 個欄位；不改角色權限契約。
保留 Web175 的映像錯誤修正與 Engine v0.183.333；不改登入或主機防火牆。
Catalog 正式 main CI 37177694304 已驗證來源 d708579092eae0fd03b2750ac594ff0396cf563b、
39 個 integration cases 兩次通過與可重現 archive；正式發布 run 37178033799 成功，
匿名公開讀回已核對兩個 assets 原 bytes、兩 binary／LICENSE 與來源；元件已正式發布。
Server514 正式 source 為 076aa43c6b978dfe65cd0fb3a05efc97ec5d02dd，不可變映像為
ghcr.io/pasturestack/server:v1.6.514@sha256:45712644bc11325df927d10bdbab47421168cc3c512eb5f2a51d85020671a71f。
正式 publisher37179046649
及獨立公開讀回完成；成品／runtime／security 的實際結果與座標列於本版 release notes。
Quick Start 對齊此不可變映像；測試站8080已升級514/Web176，首次啟動11次／重啟9次
探測均HTTP200/pong，環境參數、資料卷及五張核心表筆數保持不變，512回滾點保留。
實際Catalog遷移的兩次只讀核對一致：移除12筆空Git stub與2筆README-only項目，
有效來源、範本key、版本、內容及labels保留；無手動SQL修復。這不是完整原生流程PASS。
繁體中文與英文的新增 VM／容器表單已完成 8 組實機案例、2 組 INIT 勾選／還原及
3 次資料保護核對；必填映像錯誤可見，INIT 無欄位重疊。此項沒有建立或啟動 VM，
也不代表其他語系、GPU 或所有資源寫入流程通過。
測試站已限定驗證網路服務的編輯與清理，以及既有目錄升級的後續步驟與清理。
容器唯讀及無目標環境權限使用者的預期拒絕已分別確認；擁有者的原生啟動、重啟、
日誌、終端及刪除已分段取得實機回應，日誌與終端都有實際 WebSocket 輸出及正常收尾。
刪除確認視窗已正常關閉，另以只讀查詢確認容器及六筆關聯紀錄均已移除或清理。
這項清理觀察不等於完整歷史資料保護通過，也不把分段結果合併成完整通過。
環境停用、啟用及移除介面已分段
觀察，並獨立確認測試資料清理；這不代表完整歷史資料保護驗收通過。
完整權限／語系／版面矩陣仍未完成（INCOMPLETE），不等於正式公司站或全功能通過。
升級前請備份資料；交易重建可能更換 Catalog DB 列及 API 範本 ID，須依相同來源、
範本 key、版本、內容與 labels 核對，不承諾 ID 穩定。
詳見本版範圍及升級注意事項。
本版封裝 Web Console 1.6.175，修正一般容器／VM 映像補正或切換語系後，
父表單仍留有舊 required 錯誤的問題。只刷新同一表單自有的 validation aggregate；
model／command 錯誤及後續 backend save 錯誤保留，不改共用 NewOrEdit、
save lock、payload、Engine schema、角色或登入契約。
Web175 正式 source 為 bb905d092700c262497b88f5773e7714fc1f4be4，
tree 為 b2b38347e5fa24bd945706fd2aaab0136ea4ef45；
正式 CI37163340764
通過 821／821，fail／skip／todo 為 0；兩次 production 成品一致。
數字 tag 1.6.175
已簽章發布，匿名公開 archive 原 bytes 與 CI 一致：2982158 bytes，
SHA256 9833467b2be47d4fa01f09954fcd35beb292c59d382d5c1aecd76d17c6a387a2。
Server513 正式 source 為 eefc84d670188f8d81978d6ce600d1c0400fe720，不可變映像為
ghcr.io/pasturestack/server:v1.6.513@sha256:d6df82fe1ec29d720af47fe62ec83dcf0f96ce1b0dcfc00059363f8621dc61ab。
正式 publisher37164995463
及獨立公開讀回通過：23 assets／22 SHA-256、單 runtime layer、SBOM來源／digest核對，
隔離首次啟動13次／重啟7次後 HTTP200/pong、34 MFA/API、TLS1.2／1.3，
不信任TLS憑證拒絕與private API no-store通過；這不是QA部署或原生UI驗收。
本版merged-rootfs scan為raw52／VEX51，保留8 Medium vendor package findings／4 CVEs，
untracked／Critical／High／available-fix／secret均0，review deadline維持2026-10-20；不宣稱零CVE。
Engine 維持 v0.183.333，四 build stages／最終單 runtime layer、
460 digest-pinned base、其他 component pins 及安全門檻不變。
Quick Start更新為513 exact digest；QA目前仍512，513尚未部署，不借用歷史QA PASS。
完整功能矩陣 INCOMPLETE，原生UI／角色／VM開機仍待驗收，舊 HOLD 不升格。
詳見已發布發行說明。
本版只將 Web Console 更新為 1.6.174：全新VM表單不再預填一般容器映像，
也不顯示Ubuntu／Alpine容器quick picks；保留自訂映像、initialValue、VM last-used，
以及一般容器預設。VM boot-image說明與VM／容器缺少映像訊息沿既有i18n fallback；
必填驗證仍由原生willSave阻擋，不新增VM runtime、映像白名單或權限變更。
Web174正式signed source為 d24b7f4e164f058e3ef9057347caa2080e2b5407，
tree為 c408e8b018d99db2ca228203880f4e72663ab1b7；
正式CI37152802665
通過817／817，fail／skip／todo為0。
數字tag 1.6.174
已簽章發布；匿名公開archive原bytes與CI成品一致，2982022 bytes，
SHA256為 6408775898f412e4b27092eeddd9cdc2028ad7b27835f489139c2d0cf62c6776。
Server source為 c533ac7753d222abb515848effc27d007bd700b6，不可變映像為
ghcr.io/pasturestack/server:v1.6.512@sha256:805078de83c0320c751dff90304bd841b8e64bec720079198258d22fa41d0145。
正式publisher37153784888
與公開成品讀回通過：23 assets／22 SHA-256、public tag／digest／config一致，
隔離映像首次啟動12次／重啟8次探測後均HTTP200/pong，34項MFA/API、
TLS1.2／1.3、private no-store及不受信任TLS憑證拒絕均核對。
這些是本版成品證據，不代表全部前端權限、資源寫入或實機VM生命週期已驗收。
Engine保留正式 v0.183.333、460 digest-pinned base、多stage build與最終單runtime layer；
其他component、runtime ENV、volumes、AppArmor及安全exact-set不變更。
本版merged-rootfs scan保留raw52 findings、VEX51、8 Medium package findings／
4 vendor-pending CVE，複核期限2026-10-20；Critical／High、available-fix、untracked
與secrets均為0，不宣稱零CVE。Quick Start對齊本版已核實的不可變映像；
歷史scoped結果與HOLD不重寫或升格。完整功能矩陣仍未完成。
詳見Server512發行說明。
本版封裝 Web Console 1.6.173 的原生 Project Template 卡片名稱修正：
template choices 使用模型既有 name，不再讀取未實作的 localizedName。
Web173正式 source為 c8b8bb2659fdad3539cf6a72866c94a77ec516b6，
tree為 f590310e157edea79de81fcf333e8b39dbc5677e；
正式CI37115288389
通過812／812，fail／skip／todo為0；兩次production成品逐位元一致。
CI archive SHA256為
a566684e6e0831630a15cb7212989c0e9fe707ed07965156c2b664b9cdb5ba27；
數字tag 1.6.173 已簽章發布；匿名公開byte讀回與該SHA256一致，
詳見Web Console發行。
Server source為 e995f8f35bc6335effaceb6c973f7915c68df2ab，不可變映像為
ghcr.io/pasturestack/server:v1.6.511@sha256:bce474ce4403398044a7c24aafe6c8314bac38b44731540c5ffaa2dfc40699cd。
正式publisher37116124788
與公開成品讀回通過：23 assets／22 SHA-256、public tag／digest／config一致、
單runtime layer；隔離映像首次啟動13次／重啟9次探測後均HTTP200/pong，
34 MFA/API、TLS1.2／1.3、private no-store與不受信任TLS憑證拒絕均核對。
實際成品scan保留raw52 findings、VEX51、8 Medium package findings／4 vendor-pending CVE，
複核期限2026-10-20；Critical／High、available-fix、untracked與secrets均為0，
不宣稱零CVE。Engine保留正式 v0.183.333、460 digest-pinned base與既有安全exact-set，
不變更角色、schema、production環境或持久volumes。
QA125/8080升級與獨立只讀核對通過，首次啟動11次／重啟10次探測後HTTP200/pong；
既有binds、environment、unless-stopped、docker-default與五項DB計數保持。
映像未定義Healthcheck，不宣稱Docker healthy。
當版既有Template117原生只讀proof已通過：3 Full17/14 guards、0資源寫入，
source-bound proof核對同一ID及空stacks/services；這不是native create finalizer。
當版Process原生list/link/detail及同一ID direct GET只讀驗收通過：兩API roots×六角色
共12/12格、0資源寫入；僅涵蓋一個實際ID，不代表所有ID或write操作。
當版全新Project key 1c6998 已獨立核對為
DERIVED_SCOPED_KEY511_VERIFIED_NOT_ORIGINAL_PASS：同一次實機child有4筆原生寫入、
13 guards、6筆停用／刪除前cookie-free issued Basic GET、4 barriers及18項首次交付判斷。
原parent因QA child receipt的 resourceId／generatedKeyId schema失配仍保留HOLD；只讀derived核對
未重寫原件或重跑寫入，詳見發行說明的證據與範圍。
原生Project／Host及完整矩陣仍待各自驗收，部署或key scoped結果不代替其他流程PASS。
歷史scoped PASS與HOLD不移植為511成功，fullMatrix仍 INCOMPLETE。
Quick start對齊本版已公開核實的完整不可變映像；510與既有回復說明保留。
詳見發行說明。
本版封裝 Web Console 1.6.172 的 request-local create-only delivery：首次201
限定欄位交給本次 save 的非 canonical clone，不要求 canonical store 永久保留 secret。
Engine 維持已發布的 v0.183.333，460 digest-pinned base、最終單 runtime layer、
所有既有 production 環境與持久 volumes 契約不變。
Web172 已正式發行，CI 808／808 通過，兩次 production 成品一致，公開下載與
CI 檔案逐位元吻合；封裝 pins 已固定，沒有本機重建。
Server source 為 1a323f5f690ed89a4f03e7ead1ad2e51ddeb4fdf，不可變映像為
ghcr.io/pasturestack/server:v1.6.510@sha256:82e4ee7fa51dae3fb6b1f339ee794d17b593f6feae2fd313ef5354ccaaf2d89f。
正式 publisher37110936143
與公開成品讀回通過：23 assets／22 SHA-256、public tag／digest／config、
單 runtime layer、34 MFA/API、首次啟動／重啟及 TLS 證據均核對。
新成品 SBOM 與 scan 對齊本版，保留 raw52 findings、VEX51、
8 Medium package findings／4 CVE；不放寬門檻，也不宣稱零CVE。
QA部署、全新 key 四筆原生生命週期與 Host 流程尚未驗收；
509 scoped PASS與6982 HOLD不升格，完整矩陣仍 INCOMPLETE。
Quick start 對齊本版公開核實的不可變映像；公司站未部署或修改。
詳見發行說明。
本次修正 Engine API 回應的共用 create-only 邊界：只有真正的資源建立 （POST 且沒有 action）可以首次交付建立時限定欄位；停用等 POST action 不得再回傳該欄位。API Key 的首次金鑰交付維持原有行為，不改角色授權、 資料庫 schema、OIDC、MFA、主機防火牆或使用者的部署參數。
封裝已正式發布的 Engine v0.183.333，Web Console 保持 1.6.171。
Engine exact source 0d94f7d879d314235e582a7f4062914a27b82709，
WAR SHA256 8c42c0982cbc2f4569fa265ad320b341551758cb4fc0bc6d79ba06d70e20d328；
正式 CI273 suites／1164 tests、隔離啟動與六個發行檔案讀回已通過。
Server source 為 261bb23c980f5f896375923233e36f6554b99751，不可變映像為
ghcr.io/pasturestack/server:v1.6.509@sha256:d934c9d7bc7387626fedca5d403210fac70b7b4e35e334dcdb439f79f555ab87。
正式 publisher37105881483
與公開成品讀回通過：23 assets／22 SHA-256、public tag／digest／config、
單 runtime layer、34 MFA/API、首次啟動／重啟及 TLS 證據均核對。
成品保留 raw52 findings、51 VEX statements、8 Medium package findings／4 CVE；
Critical／High 為0，不宣稱零CVE。
QA8080 的509部署與唯讀驗收通過：首次啟動13次、重啟9次重試後均為200 pong，
環境變數、執行設定與五表筆數不變；508回復容器及資料庫備份保留。
owner2513 的既有 Account6974 續接通過：本次 PUT200／deactivate202／DELETE200，
3筆原生寫入、9個full16／14守門，cleanup=true；原508建立POST201與HOLD保留。
既有 Project6977 續接移除通過：本次只有 DELETE200／4個守門，cleanup=true；
原508 POST201／PUT200／deactivate202不算本版新寫入，原HOLD不升格。
全新Project API Key仍HOLD：第二次僅POST201建立1c6982，3個守門與Store barrier通過，
Web171原生首次交付timeout；無issued Basic讀取、edit／deactivate／delete或cleanup。
active資源保留，不自動重試或清理；第一次0資源寫入的前檢HOLD也保留。
Web172首次交付修正尚待正式打包與驗收，不包含在本版不可變映像中。
全新隔離Host原生註冊／healthy／停用／移除仍pending；空template首次0writes／0guards HOLD，
不能用guest readiness、template或Project fixture替代Host PASS。
上述scoped結果不代表Docker healthy、公司站部署或完整矩陣PASS。
完整權限、所有資源 ID、所有語系與 UI 版面矩陣仍未完成；508 scoped PASS 與歷史 HOLD 不升格。
Quick start 對齊本版已核實的完整不可變映像；公司站未部署或修改。
詳見發行說明。
本版封裝 Web Console 1.6.171，來源固定為
fc37f5af9320e492bec7e7244cd62144908b720e。API-store compatibility revision 5 僅在
新建請求的 HTTP 201、精確 type／server-generated ID、相同 Store generation／base URL
且已有該模型時採用 canonical cache，避免較晚的初始回應覆寫先到的 WebSocket 更新。
沒有相符 cache 或非新建 201 時仍走原匯入流程；GET／PUT／action／204／errors 保留。
不改 API 回應、狀態排序、訂閱、Auth 或角色授權，也不為此追加 GET。
Web171 已正式發布，CI 37094728912 通過802/802測試，含10項新回歸、
100次決定性barrier與22項audit self-tests，CodeQL通過；公開archive SHA256為
49fac41ca93eb628d0877104f9512ef382ffd9dbc89e04c940196b3a9c57798b。
Server source為 69744f3ef0c00c14147fb83480306e07ccb667d9，不可變映像為
ghcr.io/pasturestack/server:v1.6.508@sha256:e24f9993593bb609a7a0e26dc12fbbb21ab402b73c60af28955b988b83b6ac04。
正式publisher37095694250
與正式讀回已通過：23 assets／22 SHA-256、public tag／digest／config一致、
單runtime layer、34 MFA/API、首次啟動／重啟HTTP200及TLS證據皆核對。
Server安全結果保留8個Medium package findings／4 CVE與51個VEX statements，
不宣稱零CVE。QA8080已部署本版：首次10次／重啟9次探測HTTP200/pong，
runtime、environment及五表counts差異0，原三named volumes、AppArmor、
restart policy與507回復點保留。Docker health為null，不宣稱healthy。
Registry member原生建立／編輯／取消／移除已分項通過（5次原生成功寫入，
另2次API憑證收尾）；英文憑證必填驗證／取消通過且零資源寫入。
原生Volume同ID建立→Store→刷新→跨角色權限→取消→刪除已通過可追溯續接驗收：
原生POST201與DELETE200各一次，readonly兩版DELETE405，no-access兩版GET／DELETE403。
繁中／英文拒絕訊息可讀，16個生命週期資料守門（12個既有證據＋4個本次守門）通過；
本次另有5個no-access畫面／終態守門，僅刪除本案隔離Volume，其他資料保持不變。
既有API拒絕證據不重送，歷史HOLD與未證實的舊登入轉換不追認成功。
Engine 保持 v0.183.332／原 WAR，完整 pool/mount 關聯、inactive fixture、
安全閘門與回復契約保留。完整矩陣仍 INCOMPLETE，歷史 HOLD 不追認成功。
Web建置audit保留7 High／3 Moderate／0 Critical，精確上游待補風險複核至2026-10-10；
不宣稱零CVE或runtime整體不受影響。本版發布時的Quick start曾對齊508完整不可變映像。
詳見發行說明。
本版封裝 Web Console 1.6.170，修正未配置 local Volume 分類器
對 nullable 關聯欄位的處理。Web 來源為
09df1480c5f4b58c6a9a9060ff94d980792f7015；正式 CI 37082272427 的兩個 production archive
SHA-256 相同：900974b07bb20ba5b2e7c1dede7012a53c6e2c96cd094c67cb7019434c4f27c9。Web170 公開發行已讀回核實；
Server source 為 34287791861643ba93edd9923fa11dd504172f60，不可變映像為
ghcr.io/pasturestack/server:v1.6.507@sha256:c0ee312207e38f4e31b8503521c0e43cbf178110e91fac61c23056026603c91e。
正式 publisher37083174895
與公開成品讀回通過：23 assets／22 SHA-256、單 runtime layer、首次啟動與重啟、
34 MFA/API 檢查、TLS 與成品 SBOM／安全閘門。這不是原生生命週期或完整矩陣的證明。
Engine 保持 v0.183.332／原 WAR；API／Auth、角色授權、資料、完整
pool/mount 關聯檢查與安全門檻不變。完整矩陣仍 INCOMPLETE，既有 HOLD
不追認成功；Quick start 對齊本版不可變映像。
詳見發行說明。
QA8080 已完成本版部署與讀回：首次9次／重啟8次探測HTTP200/pong， runtime、environment與五表counts差異皆0，三named volumes及506回滾點保留。 Docker health為null，不稱healthy。首次嘗試因QA根分割區100%滿失敗並回滾； 僅精確回收三份未被容器引用且可由公開digest重新取得的舊image副本，原失敗紀錄保留。 新嘗試加入至少3GiB可用空間與已存在精確本機映像的守門，不涉及資料卷或VM刪除。 另以本版實測兩筆既有隔離Volume：Store／列表／刷新、取消刪除零寫入、 唯讀兩API根DELETE405、owner原生DELETE200及刷新後消失均通過。 主機新增入口restricted／readonly／noaccess的繁中、英文拒絕分項通過； 新建Volume仍在追查，完整角色矩陣仍INCOMPLETE，不以部署PASS代替。 另外精確移除10個已停止的舊Server回滾容器，保留目前507與最近506回滾點； 主機清單重新登入及刷新後只顯示這兩筆，不再堆積舊項目。未刪除VM或資料卷。
本版封裝 Web Console 1.6.169，修正合法本機磁碟區的 externalId
被誤當配置關聯、建立成功後不出現在未配置清單的問題。Engine 保持
v0.183.332；不改權限、登入、API、主機防火牆或持久資料。既有的完整
儲存池與掛載關聯檢查仍保留，未配置的 inactive 磁碟區使用正式 remove
流程，不強制轉態。Server source 為 3cfb920a428fc2af6af6a07a832d6882663f544d，
不可變映像為
ghcr.io/pasturestack/server:v1.6.506@sha256:f6860a1d0e96587b05afbf72d52c063921ff8473a976552c6d0a01d223a7a188。
正式 publisher 37079727511
已通過建置、啟動／重啟、MFA/API、TLS、單 runtime layer 及成品 SBOM／安全檢查。
Web169 正式 CI 為791/791；QA8080首次啟動與一次重啟均HTTP200/pong，
參數、掛載與五項資料筆數保存，health=null；原生瀏覽器生命週期與完整角色矩陣仍須分開驗收。
第一輪 publisher37079232161的來源gate失敗保持歷史，不追認成功。
詳見發行說明。
已正式發布，封裝 Engine v0.183.332，Web Console 維持已發布的 1.6.168。
Server source 為 400f7dc8d533a5f13a555398c595b9ae42e0c454，不可變映像為
ghcr.io/pasturestack/server:v1.6.505@sha256:b3dd402cfd773b4d37ecf06f716187833e56cc6f211b7ab920dccf8dcb7366c5。
正式 publisher 37072151759
及公開成品讀回通過：23 個 assets／22 項 SHA-256、image/component identity、
單 runtime layer、34 項 MFA/API、TLS 與成品 SBOM／安全門檻皆核對。
隔離映像首次啟動／一次重啟均 HTTP 200/pong，分別在第 10／6 次探測取得；
這不是 QA8080 部署或 Docker healthy 的證明。
8080 的版本綁定讀回確認：504 的 v1 與 v2-beta Volume schema 都缺少
isNative，不只是驗收工具的 v1 假設。這讓前端無法安全判定未配置 local
Volume；不能把缺少分類當成 false。
Engine 修補在共用 user overlay 與 frozen v1 schema adapter 恢復 server-owned
唯讀 volume.isNative，保留資料庫實際 true／false 與既有 server default。
不新增 create/update 權限，不改其他欄位、methods、actions、環境隔離或
資料庫 schema。Engine 正式 source 為 7a625eee58fb2bdba83d2f008bdf7dd3c0ae4295，
WAR SHA-256 為 31090699e214f8e357f7fe413ce307e722b9b53177003e5de0bbbca1bc7bc3f5。
正式 CI 通過270 suites／1,150 tests，fail／error／skip 皆為0，含6個新增回歸。
QA8080 已部署本版；首次啟動與一次重啟均 HTTP 200/pong，部署前後的
runtime／環境參數與五項資料筆數一致，504 容器與資料庫回復點保留。
Docker health 為 null，不稱為 healthy。原生 Volume 生命週期仍在驗收，
完整資源／角色矩陣仍未完成，不以正式發行或單元測試宣稱完整矩陣通過。
未配置 local Volume 可以合法處於 inactive；清單不要求先啟用，移除依
當次 API action 與實際關聯判斷，不為驗收額外執行啟用或停用。
Quick start 已對齊本版不可變映像。部署參數、OIDC/MFA、 多階段建置、單 runtime layer 與安全門檻不變；不使用 runtime patch。 Vendor-pending 8 個 Medium package findings／4 個 CVE 與2026-10-20複核期限保留， 不宣稱零 CVE。詳見發行說明。
已正式發布，固定封裝 Web Console 1.6.168。Server source 為
e33ef8565ebe40dd188170baa46da8092fc131b9，不可變映像為
ghcr.io/pasturestack/server:v1.6.504@sha256:11393d4a5189601464d2a2e1ffc823160bedd6bda6c1fbae12457337f7cb9e2f。
正式 publisher 37063207602
通過啟動／重啟、34 項 MFA/API 檢查、TLS、單 runtime layer 與成品 SBOM／安全門檻；
23 個公開 assets、22 項 SHA-256 與匿名 registry／component identity 已讀回。
本版修正 Volume 新增入口：只有目前環境與當次 schema 相符，且 schema 允許建立 Volume，才顯示新增控制並允許直接新增網址；既有 update 分支也須 通過相同的 schema 新鮮度條件。Storagepools 提供獨立的未配置 local Volume 區段與原生 Add，不依賴任何 pool 存在；顯示未配置前必須讀回實際 advertised storagePools 完整 collection，並以包含 inactive mounts 的完整 scoped 資料 證明未被配置或使用。原始403、network／sync error 不吞，交既有 route／growl 診斷，不能將缺漏欄位或失敗當成空關聯。只有目前 project/schema 相符且實際 advertised deactivate 的資源才開原生停用；active→detached 後沿用原生刪除。
Web168 正式 CI 37061716638 已通過788／788個 QUnit案例，fail／skip／todo皆為0，
包含16個 scoped Volume案例；兩次 production build archive SHA-256相同。
測試環境 8080 的首次啟動與一次重啟均取得 HTTP 200/pong；runtime、環境參數、
既有掛載與五表 counts 差異皆 0，503 停止回復容器與資料庫備份保留。
Docker health 為 null，不能稱為 healthy。這些證據不代表 local Volume
原生建立／列表／清理或完整角色矩陣通過；首次原生驗收因工具對 v1 schema
欄位的假設中止，資源寫入為 0，該 HOLD 保留並待修正工具後重新驗收。
Engine v0.183.331／原 WAR、API/schema、後端授權、OIDC/MFA、
部署參數、相依套件與安全門檻不變。既有 8 個 Medium package findings／
4 個 CVE 與 VEX statements 保留，不宣稱零弱點或完整矩陣 PASS。
Quick start 已對齊本版不可變映像；正式公司站未部署或修改。
詳見發行說明。
Published Server packages immutable Web Console 1.6.167 for shared schema-ID lookup.
The store already normalizes schema IDs when caching them, but its synchronous
lookup previously left the requested ID unchanged. Mixed-case resource types
such as registryCredential could therefore miss their real permission schema.
The fix normalizes lookup IDs only in the schema group. Ordinary resource IDs
remain opaque and case-sensitive; missing schemas remain denied and separate
project stores are not combined. API schemas and server authorization do not
change. Engine v0.183.331, authentication/session ownership, MFA, runtime
overrides and firewall contracts remain unchanged.
Web source is dff35fc4bce340e21cac7204146a7bcb20a7b60b; archive SHA-256 is
e8e714fc06282de75a3570aac1d4d4d04a3c9478d982d0d5aaeae14efa8ebbaf.
Exact-source component validation 37012345421 passed 772/772 tests with zero
failures, skips or todo, including four new Store/schema cases, and produced
two byte-identical production archives. Official publisher
37015013747
passed isolated startup/restart, 34 MFA/API checks, TLS, single-runtime-layer
comparison and final-image SBOM/security gates. Server source is
df061d5c93d0e4fdbc0e06664493ac5328a6f596. Anonymous registry and all 23 release
assets were read back; the immutable image is
ghcr.io/pasturestack/server:v1.6.503@sha256:4a8997768c5c16a9aefdc682f906aab34417e204d622d03116e62b2fcfe0af79.
Eight Medium package findings covering four CVEs remain vendor-pending, with
review due 2026-10-20; this is not a zero-vulnerability result.
QA first start and one restart returned HTTP 200/pong after nine attempts each,
with unchanged runtime settings, environment overrides, named mounts and
five-table count baselines. The immutable Server502 rollback and database
backup were retained. Docker health is null, not a healthy result.
Packaged QA confirmed GET-only registry/credential models, hidden create
controls and disabled edit/remove controls for the readonly role. The no-access
role showed the environment-unavailable screen; both roles used readable
existing permission errors. All 24 normal-CSRF v1/v2-beta write-denial checks
passed (12 readonly HTTP 405; 12 no-access HTTP 403). This is exact-fixture
coverage, not all API authorization or complete native-browser acceptance.
The registry/credential packaged QA on 502 stopped before resource writes
when the credential model could not resolve its schema. That HOLD is preserved;
the full permission/resource/locale matrix, including thirteen-locale inactive
badge and remaining native lifecycle checks, remains INCOMPLETE.
See the release notes.
Published Server packages immutable Web Console 1.6.166 to translate the
previously omitted Inactive state label in all thirteen supported catalogs.
The component's exact-source validation passed 768/768 tests and produced
byte-identical archives. Web source is
b63fa15f6726cb78659ae43258dfc802b30d6d04; archive SHA-256 is
9205fbaec6e80f31846212f0949c3eac0fae083f80c6c46a3122d64c4d9da6c6.
Engine v0.183.331, API/schema, authorization, authentication, runtime settings,
icons/colors, health/connection overrides and security thresholds are unchanged.
No database migration or runtime patch is required. Official publisher
37003831065
passed startup/restart, 34 MFA/API checks, TLS, single-runtime-layer comparison
and final-image SBOM/security gates. Source is
d89d585a3901b044039a685edd6140835bccb08c. Anonymous registry and all 23 release
assets were read back; the immutable image is
ghcr.io/pasturestack/server:v1.6.502@sha256:ee6d0141574280473cb27a638814ae924b3d5bfe344f1ee0e1741aae0f3efddb.
Eight Medium package findings covering four CVEs remain vendor-pending;
publication does not mean zero vulnerabilities or complete packaged UI acceptance.
The broader permission/resource/locale matrix remains INCOMPLETE.
See the release notes.
Published packaging of Web Console 1.6.165 corrects ambiguous truncated
container names on Host cards. Full names wrap within the existing shared
container/VM subpod; IP addresses and action triggers retain separate space.
Web source is 00bcd9fdc92afead708dffb4a2b3b01f4ebaeaa0, with archive SHA-256
5baaa4879fe5548cc8b66cd1c7a2005edf586d4b5f12b6dbb3796b6692e41959.
Official Web validation passed 767/767 cases and produced identical archives;
four focused CSS cases passed 744 assertions. Engine v0.183.331 and its exact
WAR, authentication, permissions, API/schema, deployment settings and security
thresholds are unchanged. No migration or runtime patch is required.
Official publisher 36980705366 passed source, single-layer comparison,
startup/restart, 34 MFA/security API checks, TLS and final-image SBOM gates.
Immutable source is ea97b199801c277efc178430b4aa6a0d4f67d25b, image
ghcr.io/pasturestack/server:v1.6.501@sha256:0a671e2695eecc74d79ef666267a40e81172205f0f8b1d0b12a7dbbed446becd.
All 23 public assets and 22 SHA-256 entries match. Eight Medium package
findings / four CVEs remain vendor-pending; this is not a zero-CVE claim.
QA first start and one restart returned HTTP200/pong with unchanged runtime
settings and database counts. Native Host-page initial/reload verification
matched six full Docker IDs/names; all five rollback suffixes are readable and
IP/action areas do not overlap. The actual menu opened/closed normally, with
zero resource writes or page/console/loading errors. WebSocket connected and
an actual server message was received. Root reviewed both actual screenshots.
This is scoped acceptance, not the broader permission/resource/locale matrix;
that matrix remains INCOMPLETE. Server500's visual HOLD below is not promoted.
See the release notes.
This patch packages Engine v0.183.331 to correct imported-container name
synchronization for normal stopped/inactive mappings. Only the name-only
full-row CAS lifecycle predicate changes; authentication, permissions, schemas,
managed-service names and Web Console 1.6.164 remain unchanged.
No migration or runtime patch is required. The immutable image is
ghcr.io/pasturestack/server:v1.6.500@sha256:7ffd67a7f82da0d374d7846b97b5a2fb71647ad01a159120418544591899f5f5,
from Server source abdee460eb67c8cd02a2db8e9a55b15f58020d83.
Publication run 36973764295
passed exact build/flatten, isolated first start/restart HTTP 200 / pong
(13 and seven attempts), 34 MFA policy/API checks and TLS 1.2/1.3 checks with
untrusted certificates rejected. Public readback verified 22 checksummed files
plus their manifest and the one-layer image/component identity. The unchanged
merged-rootfs gate retains 52 raw findings and eight exact Medium vendor-pending
package findings (four unique CVEs), with zero untracked, Critical/High,
fixed-available or secret findings. This is not a zero-CVE claim.
The exact Engine331 WAR is 87,700,088 bytes, SHA-256
0c8310d9e9a872589972658d2fd8cb88f59f473ab8072a4746df5b0f4ef9e70e,
from source 515a5d37a1194f827bc3ffde34db729905ecb2b1; its 268 suites /
1,144 tests passed with zero failures, errors or skips.
QA500 first start/restart returned HTTP 200 / pong (nine and 10 attempts),
with zero runtime-contract or tracked five-table count differences. Original
environment overrides, three named volumes, docker-default AppArmor and
unless-stopped restart policy were preserved; Docker health is null, not
Docker healthy. Server499 is retained and stopped for rollback.
Native Host1 initial/reload checks found five unique full Docker IDs, names and
links, with no removed mappings, resource writes or browser/console errors.
WebSocket received a forwarded server message. Visual review still found four
rollback names truncated to indistinguishable prefixes; visual acceptance is
HOLD pending a scoped Web Console layout correction, not a complete fix.
Historical 499 name failure and browser HOLD remain recorded, not promoted;
the full resource/role matrix remains INCOMPLETE. No company-site, all-page or
all-locale acceptance is claimed. See the release notes.
This release packages Engine v0.183.330 from source
3f7320a8063a5471618be5b8be6a168f49559847 to synchronize eligible standalone
imported-container names with fresh, full-ID Docker inspection. Managed-service
logical names and unrelated instance fields are not changed. Web Console
1.6.164, existing role/schema protections, authentication, deployment settings
and security thresholds remain unchanged.
The exact CI WAR SHA-256 is
c01cbbfd63625fc09f39c5494775919aad6db22c92050b217b28b940b57e1de3.
The immutable image is
ghcr.io/pasturestack/server:v1.6.499@sha256:8552137dd4e40bf20dee5524cabf09540ed7431328e584ca1e488065e6fec394,
from Server source 0a656e617c51059b92fb37a9b0571f142e8463aa.
Publication run 36969193015
passed the exact build/flatten, isolated first start/restart HTTP 200 / pong
(12 and eight attempts), 34 MFA policy/API checks and TLS 1.2/1.3 checks with
untrusted certificates rejected. Independent public readback verified 22
checksummed files plus their manifest, the one-layer image, version/source/digest
labels and SBOM identity. The unchanged merged-rootfs security gate reports 52
raw findings and eight exact Medium vendor-pending package findings (four unique
CVEs), with zero untracked, Critical/High, fixed-available or secret findings.
This is not a zero-CVE claim.
Engine330's signed numeric release and six exact CI assets have been verified;
the exact WAR passed isolated H2 startup without platform data or network access.
QA499 first start/restart returned HTTP 200 / pong (nine attempts each),
with zero runtime-contract or tracked five-table count differences. Original
environment overrides, three named volumes, AppArmor and restart policy were
preserved; Docker health is null, not a Docker healthy result.
Targeted name acceptance did not pass: Engine330 incorrectly requires an active
mapping for stopped imported containers, whose normal mapping state is inactive.
The retained rollback containers consequently still show their original name;
they were not deleted or manually renamed. The browser HOLD is retained, and
the lifecycle correction requires a new immutable release. These results do
not establish the full
resource/role matrix, all-page/all-locale or company-site acceptance. Historical
HOLDs remain HOLD. See the release notes; the
498 evidence below remains historical to that release and is not promoted to
499 proof.
This release packages Engine v0.183.329 to protect GenericObject capability
fields from readonly/restricted roles in v1 and v2-beta. Owner/member/service
storage and the typed Receiver API remain intact. Web Console 1.6.164,
Webhook Automation Service 0.10.3, OIDC/MFA/session ownership and deployment
settings are unchanged. The exact Engine WAR passed its normal CI build's
266 suites / 1,123 tests with zero failures, errors or skips. See the
release notes for exact component pins.
The immutable image is
ghcr.io/pasturestack/server:v1.6.498@sha256:bd8671e99fbf3661f91d6667f6cb04b16ade89a8d463ae872ffd84ce1e65a6e7,
from Server source ea58d92167eef31b76c7616f41df4d515530c359.
Publication run 36954622994
passed the exact build, flattening, isolated first start/restart HTTP 200 /
pong (10 and six attempts), 34 MFA policy/API checks, and TLS 1.2/1.3 checks
with untrusted certificates rejected. Independent public readback verified
22 checksummed files plus their manifest, the one-layer image,
version/source/digest labels and SBOM identity. The unchanged merged-rootfs
security gate reports 52 raw findings and eight exact Medium vendor-pending
package findings (four unique CVEs) after VEX, with zero untracked,
Critical/High, fixed-available or secret findings. This is not a zero-CVE claim.
The recorded QA498 8080 upgrade ran this immutable 498 image / Web Console 1.6.164.
First start/restart returned HTTP 200 / pong (11 and 10 attempts), with zero
runtime-contract and tracked five-table DB-count differences. The original
three named volumes, environment overrides, docker-default AppArmor and
unless-stopped restart policy were preserved. Docker health is null, not a
Docker healthy result; count preservation is not a whole-database comparison.
The previous v1.6.497 rollback container is retained and stopped. Limited
Receiver role/API/header/message gates passed in scoped QA: member retains
privileged reads; restricted/readonly typed reads preserve safe configuration
and hide URLs, while GenericObject exact/list reads omit key/resourceData in
both API versions. No-access exact API requests return 403. Member Add is
visible; restricted/readonly Add is hidden, and direct-create denial and
no-access unavailable messages were checked in Traditional Chinese. Normal
owner fixture creation/deletion and cleanup were verified. This does not
establish all-resource, full-page or all-locale acceptance; Secret and other
resources remain unaccepted for 498. Publisher smoke and QA startup alone do
not establish backend-write authorization or company-site deployment. Historical
HOLD receipts remain HOLD, and the broader resource/role matrix remains
INCOMPLETE. Preserve original volumes/settings for rollback; rolling back to
497 restores the low-role capability exposure.
The first publisher run 36953191960
failed when official OpenSSL fixes became available; that failed evidence is
retained. This release selects Ubuntu 3.5.5-1ubuntu3.7 from the
signed HTTPS 20261002T000000Z snapshot, without relaxing security gates.
The tracker retains four unfixed CVEs / eight Medium package findings.
This release packages the officially published Web Console 1.6.164, including
the 1.6.163 state-badge/relative-date locale fixes and Receiver validation-label
fixes. Engine v0.183.328, distributed-cache runtime 5.7.5, the immutable
v1.6.460 runtime base and all security thresholds remain unchanged.
The immutable image is
ghcr.io/pasturestack/server:v1.6.497@sha256:1a1f05415e50d2ea337140d89063c6d7ae993140befa5aa79c5c83922990021d,
from Server source 80d97523052aa86ec761ade8ec487c382a8d5e1d.
Publication run 36836319609
passed all 56 source gates, the exact image build, flattening and isolated
first start/restart HTTP 200 / pong, plus 34 MFA policy/API checks.
Independent public readback verified 22 checksummed files plus their manifest,
the one-layer image, version/source/digest labels and SBOM identity. The unchanged
merged-rootfs security gate reports 58 raw findings and 14 exact vendor-pending
package findings (eight Medium and six Low, six unique CVEs) after VEX, with zero
untracked, Critical/High, fixed-available or secret findings. This is not a
zero-CVE claim.
The recorded QA497 8080 deployment ran v1.6.497 / Web Console 1.6.164.
QA first start/restart returned HTTP 200 / pong (10 and nine attempts), with
zero runtime-contract and tracked five-table DB-count differences. The three
original named data volumes, environment overrides, AppArmor and restart policy
were preserved. This is count preservation, not a whole-database row comparison;
Docker health is null, and no Docker healthy result is claimed. That
deployment did not establish packaged native Receiver browser acceptance.
Publisher smoke evidence
uses a separate disposable database; QA startup does not establish backend-write
authorization or company-site deployment. Historical HOLD receipts remain HOLD;
mobile, all-language/full-layout and the broader resource/role matrix remain
INCOMPLETE. See the release notes for exact
component pins and remaining acceptance. Retain the nearest immutable v1.6.496
QA rollback with its original named volumes/settings; the existing v1.6.495
image and backups are also retained, while its obsolete stopped container has
been removed.
This release packages Web Console 1.6.162 for the Host Add Container capability
gate and translated Secret desktop table headings, plus Orchestration Engine
v0.183.328 with distributed-cache runtime 5.7.5. The Engine and embedded
cache include Jackson 2.22.3 / 3.2.3; numeric Hazelcast cluster runtime
remains 5.7.3. No API permission or stored-data migration is introduced.
The immutable image is
ghcr.io/pasturestack/server:v1.6.496@sha256:6c85435b3de8771e5adff0b247274e0f1b9fe9d66c8b91e07d55a444e5589678,
from Server source d8e0e898b08aae45e040eb085936d11de14027fb.
Publication run 36821096323
and independent public asset/image readback passed: 22 checksummed files plus
their manifest, one filesystem layer, official candidate first start/restart
HTTP 200 / pong, and 34 MFA policy/API checks. The unchanged merged-rootfs
security gate reports 58 raw findings and 14 exact vendor-pending package
findings (eight Medium and six Low) after VEX, with zero untracked,
Critical/High, fixed-available or secret findings. This is not a zero-CVE claim.
The first failed publication run remains recorded and is not promoted.
Isolated QA496 8080 deployment passed first start/restart HTTP 200 / pong
(10 attempts each), with zero runtime-contract/DB-count differences across the
five tracked tables. Docker health is null, not a Docker healthy result.
Two zero-resource-write desktop cases passed at 1440 x 1000: readonly Host
Add Container absence/Edit unavailability and the member Secret table's four
Traditional Chinese headings. Host statistics remained connecting and its
right-side table was not fully reviewed; the Secret body was deliberately
masked. These are not full-layout, backend-write authorization or lifecycle
acceptance. Mobile and all-language acceptance remain pending. Historical
HOLD receipts remain HOLD, the broader resource/role matrix remains INCOMPLETE,
and no company-site deployment is claimed. See the
v1.6.496 notes for component source/hash
identities; retain the immutable v1.6.495 image and original volumes/settings
for rollback.
This patch packages Web Console 1.6.161 to fix existing Certificate
metadata edits blocked by a masked private key. It does not change API
authorization, authentication or stored certificate material. This image is
also refreshed to Ubuntu's official libdbi-perl 1.647-1ubuntu0.26.04.3
security fix; failed candidates were not published. The immutable image is
ghcr.io/pasturestack/server:v1.6.495@sha256:ffd4d1c2a208b0bce3f9f961500ddebfdf7024bbddcf2d1e156cdbe76d30ba56,
from signed Server source 512d4b2377e34ce04a33266af19b62ed45949eda.
Publication run 36744673716
and independent public asset/image readback passed. The final image has one
filesystem layer; the unchanged security gate reports 52 raw findings and eight
exact Medium vendor-pending package findings after VEX, with zero untracked,
Critical/High, fixed-available or secret findings. This is not a zero-CVE claim.
Isolated 8080 first start/restart passed with unchanged runtime settings and
database-count baselines. Scoped owner/member Certificate browser checks passed
on isolated 8080, including Cancel, metadata Save, refresh and the in-use
delete explanation. Earlier HOLD receipts remain HOLD; current scoped evidence
does not resolve their historical foreign-baseline uncertainty. The broader
resource/role matrix remains INCOMPLETE. No company-site deployment is authorized.
See the v1.6.495 notes and retain v1.6.494
with the original volumes/settings for rollback.
Server v1.6.494 packages Orchestration Engine 0.183.327 and Web Console
1.6.160 for Certificate metadata edits and load-balancer reference protection.
The immutable published image is
ghcr.io/pasturestack/server:v1.6.494@sha256:9d1ddbe6f0c3fa11fefc141e14f419163c7bd14609163373d898ab0a857d790c,
built from Server source c3b50ad6891ebbde4612e89dd5a1114bc731431c.
Official publication run 36704785404
passed source, start/restart, security, checksum and publication gates. The 22
checksummed assets and checksum manifest match their published digests; the
final image has one filesystem layer. The merged-rootfs scan reports 52 raw
findings and the exact eight Medium vendor-pending package findings after VEX,
with zero untracked, Critical/High, fixed-available or secret findings. This is
not a zero-CVE claim.
Isolated 8080 deployment start/restart passed with an unchanged runtime
contract and tracked database-count baselines. Certificate API/browser acceptance remains
pending; this does not complete the broader resource/role matrix or establish
a company-site deployment. The runtime base, JDK, official OpenSSL security
packages, security thresholds and all other component coordinates are retained
from v1.6.493. Retain that immutable image and its original named volumes for
rollback. See the v1.6.494 notes for exact
component hashes and remaining acceptance boundaries.
Server v1.6.493 packages Web Console 1.6.159, which preserves
existing Registry passwords on username-only edits and explains that a blank
password input keeps the current password. Project and exact-resource update
checks remain unchanged. A signed Ubuntu package refresh also replaces the
inherited OpenSSL CLI, libraries, engines and provider with the official
3.5.5-1ubuntu3.6 security fix; the failed first candidate was not published.
The immutable published image is
ghcr.io/pasturestack/server:v1.6.493@sha256:61067362a2d91b791c7e80cb2ec4a5a907bc03884774d2019dccf1bf0e29788f,
built from signed Server source dc17c6f44e0624f0be324bfa0e682bb063674219.
Official start/restart, runtime security, checksums and component gates passed;
the final image has one filesystem layer. Isolated 8080 start/restart and scoped
Registry credential browser save, password preservation, three-language
control bounds and exact-ID authorization passed. Broader role/resource and
workflow acceptance remains separate; this is not a formal company-site
deployment. See the v1.6.493 notes.
Server v1.6.492 packages Web Console 1.6.158.
That version localizes Service direct-ID and Secrets load failures, and
unavailable responses to save or action requests, including HTTP 405. The
published image is
ghcr.io/pasturestack/server:v1.6.492@sha256:a50d7859aebb7d08b62a237e42e1323b3da3b9cef51ab8028d4c730d2dd87a03.
The release workflow passed candidate start, restart and security gates;
isolated 8080 deployment passed its startup/restart and baseline checks.
Broader role/resource and packaged browser acceptance are tracked separately,
and this is not a formal company-site deployment. See the
v1.6.492 notes for the exact source and
verification boundary.
Server v1.6.491 packages Web Console 1.6.157. Its
authenticated notice mount now runs when the component enters the page, so a
fresh direct-URL permission denial can move into the page flow without waiting
for another route transition. The published Web Console release asset matches
the pinned archive SHA-256. The Server image is published at
ghcr.io/pasturestack/server:v1.6.491@sha256:c484d298e5bde93b51b44acd476a725bbaa471959d1079d19331c01bc55f8705.
Isolated 8080 QA passed 14 scoped Stack and Service direct-create notice cases
with zero resource writes; it does not establish the broader role/resource
matrix or formal company-site deployment. See the
v1.6.491 notes for the exact source and
verification boundary.
Server v1.6.490 packages Web Console 1.6.156, which places authenticated
notices in the page flow between the navbar and main content. See
v1.6.490 notes for the source identity,
official archive identity, and packaged-browser acceptance criteria.
Server v1.6.489 packages the reviewed Web Console 1.6.155 source and
archive with notification placement below the navbar and a viewport width
bound for the growl close control. See
v1.6.489 notes for the exact source and
artifact identity and the packaged-image and browser acceptance criteria.
Subsequent QA showed that the notice could still cover the page title or
sorting controls; v1.6.490 addresses that layout defect.
Server v1.6.488 packages Web Console 1.6.154. Direct Stack and Service
create routes now show a localized permission notice before returning a user
without create permission to Stacks. Upgrade routes retain their separate
update permission check and notice. See v1.6.488 notes
for the source and artifact identity, validation scope, and remaining QA limits.
Server v1.6.487 packages Web Console 1.6.153. This patch tightens
project-bound write controls and localized denial feedback for the isolated
six-role QA matrix, while keeping the existing Engine, runtime base, and API
contracts. See v1.6.487 notes for the
exact Web Console source and artifact, validation scope, and remaining QA
limits. The package is not evidence that every resource-ID action passed.
Server v1.6.486 packages Web Console 1.6.152 from commit
dae731085d00f209ad4ee9419acd21d0b6d64f2a and archive SHA-256
56c147e392d40395690e925e0d8590e44de90bd7d6aaa3e6076ca75f30341486.
It uses the visible translated name label for required-field errors in Stack,
Service, and Container forms. The runtime base, Engine, API permissions, and
resource payloads remain unchanged. See the
v1.6.486 notes for the exact validation
boundary and isolated browser QA still required before claiming acceptance.
Server v1.6.485 pins the released Web Console 1.6.151 from commit
dfb9b6e799e6b88ae1bf4dd94e71ccc0a8e357ce and archive SHA-256
9cee713690d0f6064bd2490e8cd0a118a7dfb5589d588d50ebb5c443a0eff2b3.
Its Secret Edit control now follows the active resource, schema PUT, and self
link. Web Console main validation run 36416310187 succeeded. The
v1.6.485 notes distinguish that source
evidence from separate Server image, browser, and role-matrix acceptance.
Published Server v1.6.484 packages Web Console 1.6.150 from source
584a548dc30f8d59bcc3f1c9aba17e7b26eff4ef and archive SHA-256
9f9de0ab54ef9ad8b4bb1dd7f08e6d4c5c1aa1373e02f231fdad5e27916695b1.
Its Server source is 32d18dcfac3e557f8c33fa83ce3522b4417a8659. The
v1.6.484 notes record the source
preparation and its original validation boundary.
Server v1.6.483 packages Web Console 1.6.149 with the unchanged Engine and
other components from v1.6.482. Secret Edit shows its immutable name
read-only and sends only the editable description. New Secret, Certificate,
and Registry resources refresh their server action links after creation.
Registry credential failures no longer repeat the parent Registry POST; an
uncertain write stays visible for deliberate recovery. The
v1.6.483 notes record exact source and
artifact coordinates, validation, isolated QA, and rollback boundaries.
Server v1.6.482 packages Web Console 1.6.147 with the unchanged Engine and
other components from published v1.6.481. Service Edit now submits only
name, description, and scale instead of its cloned launch configuration
and upgrade strategy. The scale form preserves an initial zero, while its
separate quick action sends only scale after the debounce. See the
v1.6.482 notes for exact inputs, release
evidence, isolated 8080 deployment status, and pending browser write checks.
The published image is
ghcr.io/pasturestack/server@sha256:e3ac65290f17981201a6cf2857e0f6def3eb79974746bc7110357fd87869a609,
built from Server source 3d909952d31e8577793acb7e402e10b883e1c8a6.
The isolated QA deployment is healthy before and after restart and displays Web
Console 1.6.147. A bounded owner-browser run on fresh resource IDs passed
Service Edit Cancel, Save, and an injected 503 error with retry, plus Container
and Service Remove Cancel/Confirm; it restored the baseline. This run does not
establish the six-role permission matrix or production readiness.
Server v1.6.481 packages Web Console 1.6.146 with the unchanged Engine and
other components from v1.6.480. Required-field errors on the Secret,
Certificate, and Registry forms use their visible translated labels. The
encrypted-private-key error is localized as well. See the
v1.6.481 notes for the exact scope and
isolated 8080 QA still required for browser and write acceptance.
The published image is
ghcr.io/pasturestack/server@sha256:013eb045ed669344a67b8ac85d2ce56193abb74f34628281dec503dced8ab415,
built from signed Server source 9c6914cda01a48dda4fb38f62d1a3f0c4db10be8.
Publication does not accept the pending isolated 8080 localized validation
and six-role write matrix.
Server v1.6.480
packages Orchestration Engine 0.183.326, Node Agent 0.13.27,
Authentication Service 0.4.42, Web Console 1.6.145, and Webhook Automation
Service 0.10.3. Web Console 1.6.145 resolves create capabilities across
mixed-case schema IDs, correcting the Registry Add false denial found in
v1.6.479 isolated QA. Secret and Certificate Add controls, direct Add denial,
and Secret Edit action-link behavior remain as introduced in v1.6.479.
ProjectTemplate writes remain owner-scoped for non-admins:
the Web Console shows edit/remove only for an exact owner account ID match or
an administrator, while the Engine exposes isPublic read-only in the frozen
/v1 user schema and omits misleading remove actions. Direct edit denial
shows consistent English or Traditional Chinese feedback; API-key save errors
stay in the modal without exposing key values. Container, project API-key,
and Receiver Hook write controls follow effective project capabilities.
Receiver cloning leaves the source's issued webhook URL and lifecycle state
behind, while a new private ProjectTemplate does not inherit the catalog
Default's external identity. Denied direct routes show localized feedback;
the container table keeps its actions reachable in narrow and RTL layouts.
New private ProjectTemplates are created from editable fields with deep-copied
stacks; new-resource clones omit server-owned identity and lifecycle fields.
Receiver clones omit inactive driver configuration and block unsupported drivers.
The engine carries FreeMarker 2.3.35, and the
runtime retains signed Ubuntu curl 8.18.0-1ubuntu2.7. Read the
v1.6.480 notes and
earlier releases for the
exact scope, validation, and upgrade history.
The published image is
ghcr.io/pasturestack/server@sha256:e388b0bddb4cca5a5116ba6862c6c0fffc29ee36b072d577759c43680bb87d39,
built from signed Server source ea5cb9f52ddbeb7286f1d0f3706d5f516079f508.
Publication does not accept the pending isolated 8080 Registry Add role and
write matrix.
Docker Engine 29.4.1 through 29.7.2 is supported as a bounded SemVer
interval, and 29.8.0 is supported explicitly. The effective compatibility
setting is the API's activeValue: a value saved in the database can override
a newer image default after an upgrade. Check that value when a host's support
status does not match its installed Docker version.
The Linux runtime remains a compatibility-focused release. Windows node-agent ZIPs are artifact candidates; Windows host support still requires a validated bootstrap runtime and privileged Windows VM testing. See COMPATIBILITY.md for the tested boundaries and SECURITY.md for security and release evidence.
Before deploying, verify the v1.6.516 numeric tag and immutable digest in
Server releases.
A registry login is not required. Pin the version and retain the database and
platform volumes:
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.516@sha256:3741b7d87273387f36b49e44d407c240658db0ab7fc7fb8d518ae08f55ac733cFor TLS termination at a reverse proxy, set the exact public origin so generated API links and WebSocket requests use HTTPS:
services:
pasturestack-server:
image: ghcr.io/pasturestack/server:v1.6.516@sha256:3741b7d87273387f36b49e44d407c240658db0ab7fc7fb8d518ae08f55ac733c
restart: unless-stopped
ports:
- "8080:8080"
environment:
PROXY_PLATFORM_PUBLIC_ORIGIN: https://stack.example.com
volumes:
- pasturestack-cattle:/var/lib/cattle
- pasturestack-mysql:/var/lib/mysql
- pasturestack-mysqllog:/var/log/mysql
volumes:
pasturestack-cattle:
pasturestack-mysql:
pasturestack-mysqllog:Use only an origin (scheme://host[:port]) for
PROXY_PLATFORM_PUBLIC_ORIGIN, without credentials, path, query, or fragment.
Set the reverse proxy, HTTPS, backup, and access policies for your deployment
before exposing the service. See performance settings
for supported JVM and embedded MariaDB variables.
Existing databases can retain older image, download, Catalog, or Docker compatibility settings after an image upgrade. Review effective settings and follow the upgrade guide before changing persisted coordinates. Its migration script is read-only by default; apply and rollback are explicit, and the guide requires an isolated restore first. Preserve the same volumes and configuration when changing the image tag or rolling back.
Reviewed images are published on public GHCR under immutable semantic version
tags. Matching GitHub Releases
hold versioned assets, checksums, and release evidence. Catalog templates come
from the public catalog-templates
repository at a pinned commit. Operational image references use version tags;
release records provide digests for independent verification.
Server packages pinned source commits and verified component artifacts. Local source and shell checks are:
bash scripts/test
bash scripts/check-server-source-gates.shStartup, database migration, node registration, backup/restore, upgrade, and rollback need isolated VM validation. See ORIGIN.md for source provenance. The publication workflow is manually dispatched; a published image does not by itself establish production readiness.
The web console provides English, German, Persian, Filipino, French,
Hungarian, Japanese, Korean, Brazilian Portuguese, Russian, Ukrainian,
Simplified Chinese, and Traditional Chinese for Taiwan. New server bootstrap
messages accept PASTURESTACK_LOCALE=en-US or zh-TW; protocol fields and
persisted identifiers remain unchanged.
The inherited project remains under the Apache License 2.0, with additional attribution in COPYRIGHT_DETAILS.md. Bundled components retain their own licenses and notices.