Pin socktop apt version (1.60.2-1); bump to 0.3.10
Build and Deploy to K3s / test (push) Successful in 1m33s
Build and Deploy to K3s / lint (push) Successful in 1m0s
Build and Deploy to K3s / build-and-push (push) Successful in 5m17s
Build and Deploy to K3s / deploy (push) Successful in 1m9s

Image 0.3.9 baked socktop 1.60.1 because CI's registry layer cache reused
the apt-install layer from before the 1.60.2 release. 1.60.1 has no
--no-kill flag, so the restricted shell's invocation parsed it as the
positional websocket URL, breaking (and on overwrite, corrupting) the
local profile. Pinning the package version busts the cache and ties the
installed binary to the flags the restricted shell uses.

Also point the manifest's webterm container at the current tag so a
manual kubectl apply cannot roll the image back to 0.2.2.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
jasonwitty
2026-08-24 09:16:29 -07:00
parent 768487c268
commit 6711ac030f
4 changed files with 10 additions and 5 deletions
Generated
+1 -1
View File
@@ -2609,7 +2609,7 @@ dependencies = [
[[package]]
name = "webterm"
version = "0.3.8"
version = "0.3.10"
dependencies = [
"actix",
"actix-files",