Repository navigation
Pin PHP for isolated reproducible PHAR builds - #157
Conversation
|
Frozen source/profile review requested for The new setup reuses the accepted PHAR builder/profile, parses its private outputs as data and installs a separate reproducibility wrapper. The host prepares each Git archive outside PHP writable temporary data. Runtime sees only the selected tree read-only, plus the existing narrow PHAR output mounts; sibling trees and the saved comparison artifact are not mounted. A read-only owned single-link metadata file selects the prepared tree. The original mutable Box cache argv is routed through the existing guard and pinned read-only artifact. The original two independent source archives, build commands, hashes and comparison are preserved. Four offline controls pass, covering mounts, cache argv, malformed/linked metadata and tree placement. Real replacement/Box controls and the original guarded two-build command follow on the retained image; no hosted or broader profile acceptance is inferred.
|
|
Security current source-review step is policy-blocked and set aside; no source/runtime verdict or workflow activation is claimed. |
|
Consumed local NONPASS at source All original PHAR profile controls, new archive/wrapper/metadata/comparison controls, mutable-cache predecessor/current Box execution controls and actual Composer clean-trust verification pass. The original two-build procedure fails byte equality: first SHA The finite event stream captured all 38 created container IDs. Every exact ID was rechecked as no-such-object on lab4; no runtime resource remains. The original procedure's cleanup removed both temporary trees. Logs and hashes remain separately attributed. The source correction will set Box's supported timestamp field from the same Independent Security review is separately policy-blocked/set aside (neutral record). No source/runtime Security verdict, central admission or workflow activation is selected, and this ordinary functional correction does not resume or satisfy that blocked review. |
|
Ordinary local functional correction PASS at exact The prepared driver is now separate from the byte-unchanged live legacy script. Existing live workflow code and policy are unchanged; the full current target again validates eight guarded dependency requests. The prepared tree's read-only Box configuration explicitly sets the supported timestamp from Five offline controls and both real fixture methods pass: predecessor/current archive-control, wrapper, metadata and comparison-copy refusals, required output writes/following PHP, plus mutable-cache versus pinned Box execution. The unchanged PHAR component checks, exact PHP8.4.27/Composer2.10.3 profile and actual clean-trust/TLS checks also ran and pass on retained image Both independent Git archives execute the original PHAR build algorithm and produce the same573-file PHAR SHA256 The earlier673 attempt remains separately consumed NONPASS (6869723618). This repeat follows an implementation correction and does not relabel that attempt. Security reports its source-review step was withheld by the fleet controller under OpenAI cyber policy, with no narrower condition disclosed (neutral record). That review remains set aside; no retry, alternate review route, source/runtime approval, central admission, workflow activation or merge is selected. Current ordinary CI still runs independently. Current staged source identities:
|
|
Current ordinary source/CI state is concrete at The corrected local two-build procedure and all functional controls pass; both independent PHARs have SHA256 The branch remains a draft and is retained for unfinished work. No central record, workflow activation, merge, release or independent Security approval is selected. Security reports the fleet controller withheld its source-review step under OpenAI cyber policy and disclosed no narrower repository condition or approval to clear. That review remains set aside, with no retry or alternate route selected (neutral record6869412140). Maintained2.3.x caller work remains separately tracked in shared297; the legacy macOS SPC refusal is unchanged. |
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Replace the reproducible-build job's unbound shivammathur/setup-php step with the staged container profile: setup-php-repro-container.sh, the actual Composer trust verifier, then the two-tree CI driver. The job runs on ubuntu-24.04, the qualified runner, and the fixture matches it. The ordinary local scripts/verify-reproducible-build.sh is unchanged. The release contract test now also pins the CI driver's two-tree algorithm and that this job no longer uses setup-php. Refs durable-workflow/.github#297 Co-Authored-By: Claude Opus 5.5 <[email protected]>
|



Moves the
build.ymlreproducible-buildjob off the unboundshivammathur/setup-phponto the pinned PHP container profile. This is CLI's remaining caller for durable-workflow/.github#297.scripts/build.sh pharalgorithm, with byte comparison. Each selected tree is mounted read-only with narrow writes. Box runs from the pinned read-only artifact, and the Boxtimestampcomes fromSOURCE_DATE_EPOCH. Local PASS at6be8a012: both PHARs are1d2769e2…7f30.setup-php-repro-container.sh, then the live Composer trust verifier, thenscripts/ci/verify-php-reproducible-build.sh, onubuntu-24.04(the qualified runner). The fixture matches the job. The localscripts/verify-reproducible-build.shis unchanged.ReleaseInstallerContractTestalso pins the CI driver's two-tree algorithm and that this job no longer uses setup-php.Merge order: durable-workflow/.github#410 first. It admits this head's exact source (
4df798b7). Until it merges, the Central action policy preflight fails, which is expected, and the dependent jobs skip. With #410's policy,qualification_policy.py validate --target clipasses on this head locally. After #410 merges, rerun CI. The hosted reproducible-build job is the real qualification.The release workflow's own setup-php steps and the maintained 2.3.x callers are out of scope and remain under #297. The earlier "Security review set aside" was a policy-filter refusal, not an operator stop. General took over this work while the CLI agent is off, and General reviews it.
🤖 Generated with Claude Code