chore(ci): retrigger publish-workspace-server-image after EACCES hotfix

Run #86994 (publish-workspace-server-image.yml on mc#1589 merge sha 0f0f1ba2) failed at the setup-buildx-action step with "EACCES: permission denied, mkdir '/home/hongming/.docker-ecr/buildx/certs'". Root cause: PC2 WSL publish runner (hongming-pc-runner-publish-2 id=33) sets DOCKER_CONFIG=/home/hongming/.docker-ecr/ via its envs block, but the buildx subdir under it was hongming-owned with no other-write, so the container's UID 1001 user (the act_runner job user) couldn't mkdir the buildx/certs subdir setup-buildx-action expects. Hot-patch: pre-created /home/hongming/.docker-ecr/buildx/certs with chmod 777 on the WSL publish runner. Either PC2 or operator publish runner now succeeds. This commit is trigger-only — the file change is a doc-comment in the workflow header citing the failure + the hot-patch. No functional change to the workflow logic. The push:main trigger re-runs the workflow with the now-working runner-side perms. Proper fix (per-runner DOCKER_CONFIG dir owned by UID 1001, or the internal#597 --env HOME=/home/runner pattern applied to publish runners too) is a CI-hygiene follow-up — tracked separately. mc#1589 cascade is the immediate dependency: workspace-server image needs to be in ECR before the scoped CP redeploy (only_slugs= [reno-stars,chloe-dong] + confirm:true) can pick it up for the reno-stars 94MB PDF upload P0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-20 02:27:45 -07:00
1 changed files with 8 additions and 0 deletions
@@ -43,6 +43,14 @@ on:
 # `cancel-in-progress: false`; that is not acceptable for a workflow with a
 # production deploy job. Per-SHA image tags are immutable, and staging-latest is
 # best-effort last-writer-wins metadata.
+#
+# 2026-05-20 retrigger: run #86994 on mc#1589 merge sha 0f0f1ba2 failed at
+# setup-buildx-action with EACCES on PC2 WSL publish runner — the runner's
+# DOCKER_CONFIG=/home/hongming/.docker-ecr/ dir didn't have a buildx/certs
+# subdir writable by the container's UID 1001. Hot-patched the dir perms;
+# this chore push retriggers the workflow. Proper fix (per-runner
+# DOCKER_CONFIG owned by 1001, internal#597 --env HOME=/home/runner pattern)
+# is tracked as a CI-hygiene follow-up — not in scope here.

 permissions:
  contents: read