- [2026-08-13] Stop pinning laravel installs to a mis-captured composer fixture: the
captured
composer.jsonrequiredorchestra/testbench-core ^10.xwhile these commits want^9.x, socomposer installcould not resolve and the image failed to build. Dropped the fixtures and let the repo's own manifest resolve; alsogit checkout -B master(a--single-branchclone lands on laravel's current default, which composer uses to derive the root version) andrm -f composer.lock. 9 instances:laravel__framework-51195,-51890,-52451,-52680,-52684,-52866,-53206,-53696,-53949. - [2026-08-13] Pin composer's root version for one laravel instance: composer infers
laravel/framework's own version from the checked-out branch, which now resolves to13.x-devand conflicts with the lockedtestbench-core10.2.1 (<13.0.0), socomposer installrefused the lock. SetCOMPOSER_ROOT_VERSION=12.9.9and kept the fixture, which reproduces the previously passing image.laravel__framework-53914. - [2026-08-13] Remove future commits reliably when cloning: same fix as the Verified
repo — date-based tag pruning via a
forloop (awhile readloop's git calls ate the piped stdin), plusgit reflog expireandgit gc --prune=nowso unreferenced future commits are physically gone, and a build-time assertion that no commit afterbase_commitremains. All instances. - [2026-08-13] Fall back to a full clone when a mapped branch is gone:
git clone --branch X --single-branchexits 128 once upstream deletes branch X, failing the build; retry without the branch pin. Any instance whose branch mapping goes stale.
apache__lucene-13170is flaky and not chased.