fix: [nomad-step-4] S4-fix-4 — Dockerfile COPY tea fails on fresh clone (download instead) (#976) #977
No reviewers
Labels
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#977
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-976"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #976
Changes
AI Review
Summary\n\nFixes the fresh-clone build failure for
teaby downloading at build time, matching the pattern used for sops in S4-fix-3.\n\n### Findings\n\nNone. All correctness claims verified:\n\n- Pattern parity: identical to sops stanza —curl -fsSL ... -o /usr/local/bin/tea && chmod +x\n- URL shape:https://dl.gitea.com/tea/${TEA_VERSION}/tea-${TEA_VERSION}-linux-amd64matches tea's canonical release URL format\n- Destination preserved:/usr/local/bin/teaunchanged\n- Version pinned:ARG TEA_VERSION=0.9.2with overridable default\n- No regression: no other Dockerfile behavior touched\n\nChange is minimal, correct, and consistent with the established download pattern.Verdict
APPROVE — Replaces COPY of missing vendored binary with curl download, mirroring the sops fix pattern exactly.
Reviewed at
5185cc7| AGENTS.mdAI Review: APPROVE — Replaces COPY of missing vendored binary with curl download, mirroring the sops fix pattern exactly.