Switch dev dependencies from WPackagist to WP Packages

[retlehs]

Switches dev dependencies from WPackagist to WP Packages — a faster, independent alternative that mirrors the same wp.org plugins and themes.

Why this is a natural fit

This repo already uses roots/wordpress for WordPress core, so it's already partially in the Roots Composer ecosystem. Adopting WP Packages for the wp.org-mirrored dev fixtures keeps everything wp.org-sourced under the same ecosystem.

Why WP Packages

• ~17x faster Composer resolves on cold cache (meaningful for fresh contributor setups and CI without lock cache)
• Updates every 5 minutes vs. WPackagist's ~1.5 hours
• Fully open source — application, infrastructure, and deployment all in the public repo
• Community-funded via GitHub Sponsors; WPackagist was acquired by WP Engine in March 2026
• Comparison: https://wp-packages.org/wp-packages-vs-wpackagist
• Bedrock now uses WP Packages as its default Composer source

Changes

• repositories[0].url: https://wpackagist.org → https://repo.wp-packages.org
• All wpackagist-plugin/{name} → wp-plugin/{name} (9 packages: ACF, BuddyPress, Classic Editor, EDD, Jetpack, Two Factor, User Switching, Yoast SEO, WP Crontrol)
• wpackagist-theme/twentytwentythree → wp-theme/twentytwentythree

Lock file

Scoped the composer update to only the renamed packages, so the lock diff is minimal — 10 removals + 10 additions, nothing else touched. Same pinned versions; both repos pull the same wp.org-built zips so output is byte-identical.

Happy to adjust anything.

PS. Stream is one of the most downloaded packages on WP Packages https://wp-packages.org/packages/wp-plugin/stream 🎉

Disclosure: I maintain WP Packages and Bedrock.