diff options
| author | nsfisis <nsfisis@gmail.com> | 2026-08-15 08:45:08 +0900 |
|---|---|---|
| committer | nsfisis <nsfisis@gmail.com> | 2026-08-15 08:45:08 +0900 |
| commit | 2e40eaf6bf5c4bd8eedad597e4c3b19b5457421b (patch) | |
| tree | f4a3843e0c903d4eaca3ac7882836c77a255c999 /scripts/plugin-stub-generator | |
| parent | 55f385450407a3d8c6c7c90ec4dc8995f5277a94 (diff) | |
| download | php-shirabe-2e40eaf6bf5c4bd8eedad597e4c3b19b5457421b.tar.gz php-shirabe-2e40eaf6bf5c4bd8eedad597e4c3b19b5457421b.tar.zst php-shirabe-2e40eaf6bf5c4bd8eedad597e4c3b19b5457421b.zip | |
feat(diagnose): audit the Composer runtime the executable carries
checkComposerAudit reported success instead of auditing anything, because
the binary ships no vendor/composer/installed.json on disk. It reads the one
in the embedded Composer PHP runtime now, and Composer's warning for a
missing installed.json is back.
Only that file leaves the bundle, into a temporary directory that goes away
with the handle; the runtime is unpacked whole only for a worker that cannot
read the bundle in place. Phar::extractTo's $files argument selects it,
which the shim ignored so far.
SHIRABE_COMPOSER_PHP_DIR moves into composer_runtime, so the worker and a
reader on the Rust side resolve the runtime through the same branch.
DiagnoseCommandTest::testCmdSuccess is ignored: packagist has advisories
against composer/composer 2.9.7, the version Composer::VERSION reports, so
diagnose exits 1 where the test expects 0. Upstream Composer 2.9.7 reports
the same advisories.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Diffstat (limited to 'scripts/plugin-stub-generator')
0 files changed, 0 insertions, 0 deletions
