In June, we announced that GitHub Actions was now our primary CI/CD workflow tool, and would be enabled by default for customer repositories, going forward. While we have already discontinued setting up CircleCI or Travis CI pipelines for new applications, existing applications will continue to have CircleCI or Travis CI enabled until March 31, 2026. Customers currently using CircleCI or Travis CI for their builds should plan to migrate to GitHub Actions by this date.
Why GitHub Actions?
We take security seriously, which is why we’re consolidating our tooling to reduce both our security footprint and overall system complexity. By standardizing on GitHub Actions, we’re making our workflows easier to use, maintain, and support—while also unlocking greater value for customers. GitHub Actions not only offers robust, enterprise-grade security, but also gives you access to thousands of pre-built Actions that accelerate development and simplify automation. And with new AI-powered workflows, you’ll be able to build, test, and deploy faster and smarter than ever before.
Supporting Your Migration
WordPress VIP will be focusing our October session of Developer Office Hours, on GitHub Actions. If you’re new to our Developer Office Hours, this is a series of live webinars where our engineers go deep into topics that are relevant to anyone developing with VIP, while also dedicating plenty of time to answer your questions.
VIP Developer Office Hours – GitHub Actions:
- October 15, 2025
- 1 p.m. EDT (5 p.m. UTC, 10 a.m. PDT)
For more on GitHub Actions, as well as steps to migrate, please check out these links below.