The details behind sharing a Composer cache across GitHub Actions test jobs
DanielLockyer · x · 2026-11-22
Follow-up from DanielLockyer with the full GitHub PR details behind the Composer cache-sharing change: each test previously spun up a fresh COMPOSERHOME via createTestEnvironment(), leaving the cache empty and forcing re-downloads of Packagist metadata and archives. The PR sets COMPOSERCACHEDIR to .cache/composer via putenv() in tests/bootstrap.php — effective locally and in CI, leaves pre-set values alone — and adds /.cache/ to .gitignore (the cache only holds zip and JSON files, so PHPCS and the linter won't pick it up).
More from coding & agent
- Sharing the Composer cache in GitHub Actions made PHPUnit integration tests 31% faster — DanielLockyer · 2026-11-22
- Google's Mirror Dimension: synthetic web for safe browser-agent testing — shashib · 2026-11-22
- Exposing Google/YouTube trending searches to agents via an MCP tool — Substantial-Tour-581 · 2026-11-22
- What hard stops do you put on your AI agents? A practical red-line list — Virtual_Arachnid7916 · 2026-11-22
- Stardock CEO shows Clairvoyance: hierarchies of 71 AI 'staff' agents building Sins of a Solar Empire II — draginol · 2026-11-22
- FieldCraft: pure-Rust open-source CAE tool bundles FEA, heat and fluids with MCP support for AI agents — Promptmethus · 2026-11-22