Skip to content

fix: make public Codex assets readable in restricted containers - #164

Merged
teslashibe merged 1 commit into
mainfrom
fix/public-assets-readable
Sep 4, 2026
Merged

fix: make public Codex assets readable in restricted containers#164
teslashibe merged 1 commit into
mainfrom
fix/public-assets-readable

Conversation

@teslashibe

Copy link
Copy Markdown
Owner

Scope

  • Explicitly COPY public Codex JSON assets with mode 0644, independent of checkout umask.
  • Exercise provenance smoke as UID/GID 1000:1000 with all capabilities dropped and no-new-privileges; assert both assets are readable.

Validation

  • Repository Go gate passed: gofmt, go build ./..., go vet ./..., go test -race ./....
  • Local linux/amd64 build used isolated tracked-source archive with both JSON source modes deliberately 0600.
  • Restricted image smoke passed: assets 0644 root-owned and readable; UID/GID 1000:1000, zero capabilities, NoNewPrivs=1; health and supplied build provenance matched.
  • No secrets, PVCs, or production changes. EU deployment is a separate operator handoff.

@teslashibe

Copy link
Copy Markdown
Owner Author

Release validation exception: GitHub check annotation confirms "The job was not started because your account is locked due to a billing issue." Authorized admin merge relies on completed local repository Go gate (gofmt, build, vet, race tests) and linux/amd64 restricted-image smoke with deliberately 0600 source assets, production UID/GID 1000:1000, dropped capabilities, no-new-privileges, readable 0644 assets, and verified health/build provenance. Exact reviewed head: 4c896dd; latest main: 0bdf30e. Only Dockerfile and .github/workflows/docker.yml changed. No EU deployment in this task.

@teslashibe
teslashibe merged commit 1e503fe into main Sep 4, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant