Skip to content

Harden external Docker builds with frozen lock - #17

Merged
ifuri-validator-agent[bot] merged 1 commit into
mainfrom
ticket/005-harden-docker-build
Sep 1, 2026
Merged

Harden external Docker builds with frozen lock#17
ifuri-validator-agent[bot] merged 1 commit into
mainfrom
ticket/005-harden-docker-build

Conversation

@tom-sapletta-com

Copy link
Copy Markdown
Contributor

Summary

  • pin uv 0.11.28 and Python 3.12.14 stages by immutable manifest digest
  • validate the portable no-sources graph and install production exclusively with frozen, non-editable uv sync
  • install E2E plugin metadata with no build isolation and no dependency resolution
  • complete the immutable Docker build chain for external consumers including Harden nested and external Docker build supply chain semcod/koru#64

Validation

  • no-cache production build: TestQL 1.2.67, uv 0.11.28, nlp2env 0.1.6
  • no-cache E2E build: four local plugin distributions installed resolver-free
  • E2E catalog: graphql, proto, sql entry points
  • full container suite: 1701 passed, 12 skipped, 1 warning
  • uv lock --check --no-sources
  • three Compose config checks, two Docker build checks, GOV-PASS

Closes #10
Related: semcod/koru#64

@ifuri-validator-agent ifuri-validator-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deterministic Validator approval for exact head 24fb08858c75ba3bca4fcd17fa97d64a93a0836d.

Ticket: ticket-005
Correlation ID: testql-pr-17-ticket-005
Model: zai/glm-5.3
Reviewed diff chunks: 2
Advisory LLM verdict: APPROVE
Advisory summary: Reviewed all 2 diff chunk(s). Dockerfiles migrate from pip resolution to digest-pinned uv/Python stages with frozen lockfile installs and resolver-free plugin metadata installation in the E2E image. Governance docs added. No security issues; no failed tests. | Governance/evidence files for ticket-005 (Docker build hardening). Chunk contains intent metadata and preprompt docs only; no executable code, secrets, or workflow changes. Intent file path rules are consistent with the changed files list.
Advisory findings: none
The LLM output above is advisory and was not used as the approval trust root.
Merge will be attempted after this approval when explicitly authorized.

Decision record (recomputable)

DECISION D-005-3647
TICKET ticket-005
HEAD_SHA 24fb08858c75ba3bca4fcd17fa97d64a93a0836d
CORRELATION_ID testql-pr-17-ticket-005
ACTOR agent:ifuri-validator-agent[bot]
APPLIED_RULE P-CORE-015
INPUT author_login = "tom-sapletta-com"
INPUT observed_checks = ["test=PASS"]
INPUT required_checks = ["test"]
INPUT required_checks_source = "protected registry (env/request)"
INPUT reviewer_login = "ifuri-validator-agent[bot]"
INPUT superseded_checks = []
VERDICT APPROVE AUTHORITY DETERMINISTIC
REJECTED REQUEST_CHANGES BECAUSE NO_UNSAFE_CHANGE_REASON_FOUND
ADVISORY llm_verdict = "APPROVE" MODEL "zai/glm-5.3"
ASSERT VERDICT_AUTHORITY != "ADVISORY"

@ifuri-validator-agent
ifuri-validator-agent Bot merged commit d08d033 into main Sep 1, 2026
1 check passed
@ifuri-validator-agent
ifuri-validator-agent Bot deleted the ticket/005-harden-docker-build branch September 1, 2026 23:24
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.

Harden Docker build supply chain for external consumers

1 participant