The Wire · Showcase
CLI E2E CLEANUP HITS THE BRAKES ON 429S
By RepoJournal · Filed · About Shopify
Shopify CLI just cut Accounts rate-limiting pressure by consolidating parallel cleanup jobs into a single sequential operation that reuses auth state.
The team shipped two interconnected fixes to their E2E test infrastructure. First, the auth state reuse pattern [1] stops redundant authentication during cleanup, which was hammering Accounts with concurrent login requests in CI. That gets paired with a structural fix [2] that moves app cleanup out of the sharded test matrix entirely, replacing it with a single follow-up job that runs after all shards complete. This eliminates the race condition where one shard starts deleting apps while another is still spinning them up. Both changes [1] and [2] landed in the main branch as of this morning. The engineering impact here is tangible: fewer 429s during CI runs, faster feedback loops, and a cleaner separation between test execution and teardown.
Action items
- → Review E2E test runs for reduced rate-limiting errors in next CI cycle Shopify/cli [monitor]
- → Validate cleanup job timing in sharded runs to confirm sequential execution Shopify/cli [plan]
References
- [1] Reuse E2E auth state during app cleanup ↗ Shopify/cli
- [2] Run E2E app cleanup after shards finish ↗ Shopify/cli
FAQ
- What changed in Shopify on July 1, 2026?
- Shopify CLI just cut Accounts rate-limiting pressure by consolidating parallel cleanup jobs into a single sequential operation that reuses auth state.
- What should Shopify teams do about it?
- Review E2E test runs for reduced rate-limiting errors in next CI cycle • Validate cleanup job timing in sharded runs to confirm sequential execution
- Which Shopify repositories shipped on July 1, 2026?
- Shopify/cli