Use external temporary storage for release builds
This commit is contained in:
@@ -230,6 +230,8 @@ offline suite, and compiled-export/import checks pass.
|
||||
|
||||
### R6 — Medium: Builds require a writable parent of the repository
|
||||
|
||||
Status: Resolved.
|
||||
|
||||
Category: Inadvertently strengthened filesystem prerequisite.
|
||||
|
||||
**Evidence:** [Candidate builds](../../internal/build/candidate.go), around line 21,
|
||||
@@ -250,6 +252,11 @@ adding broad output-directory restrictions.
|
||||
read-only repository parent and a usable system temporary directory. Generated
|
||||
candidate output still leaves the worktree clean.
|
||||
|
||||
**Resolution:** Candidate and CLI delivery builds use shared system temporary
|
||||
storage allocated by `internal/tempdir`, with worktree containment checks and
|
||||
caller-owned cleanup. Regressions execute both operations with read-only
|
||||
repository parents and confirm clean worktrees. Affected suites pass.
|
||||
|
||||
### R7 — Medium: Attachment origin restrictions exceed credential isolation
|
||||
|
||||
Category: Inadvertently strengthened prohibition.
|
||||
|
||||
Reference in New Issue
Block a user