Title: VIP MU plugins branches and updates
Author: WordPress VIP Documentation
Published: July 10, 2023
Last modified: September 2, 2025

---

 1. [VIP MU plugins](https://docs.wpvip.com/vip-go-mu-plugins/)
 2. VIP MU plugins branches and updates

#  VIP MU plugins branches and updates

The branch of VIP MU plugins that deploys to an environment—production branch or
staging branch—can be configured in [the Software Versions panel](https://docs.wpvip.com/software-management/)
of the VIP Dashboard.

## Production branch

VIP MU plugins is open sourced. Its development can be followed from [the VIP MU plugins GitHub repository](https://github.com/Automattic/vip-go-mu-plugins/).

## Staging branch

By default, VIP deploys the staging branch of VIP’s MU plugins to one non-production
environment for all applications. This allows customers to test changes ahead of
their release to production environments. This also provides time for the VIP Team
to observe errors and test for bugs across a wider variety of applications.

Changes made and deployed to the VIP MU plugins Staging branch are labeled `[Status]
Deployed to staging` and visible in this filtered [VIP MU plugins pull request](https://github.com/Automattic/vip-go-mu-plugins/pulls?q=label%3A%22%5BStatus%5D+Deployed+to+staging%22+)
view. 

## Release schedule

The release window for VIP MU plugins (both the production and staging branches)
is currently Tuesdays between 08:00 and 22:00 UTC (09:00 and 23:00 UTC when Daylight
Saving Time is in effect in North America).

## Changelogs

An entry is posted to the [VIP Platform Changelogs](https://docs.wpvip.com/changelogs/)
for every release version of VIP MU plugins. Changelogs for VIP MU plugins can be
reviewed by release branch:

 * [VIP MU plugins [Production]](https://docs.wpvip.com/changelogs/vip-mu-plugins-production/)
 * [VIP MU plugins [Staging]](https://docs.wpvip.com/changelogs/vip-mu-plugins-staging/)

## Branches for local development

**Local development environments _must_ include a copy of [VIP MU plugins](https://github.com/Automattic/vip-go-mu-plugins/)**.
Without it, customizations, core behaviors, and functionality tested locally can
often behave differently in a VIP Platform environment. The local copy of VIP MU
plugins should be regularly kept up to date.

 * A `git clone` of [the vip-go-mu-plugins repository](https://github.com/Automattic/vip-go-mu-plugins)
   includes [submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules). These
   must be initialized with `git submodule update --init --recursive` in order to
   work as expected.
 * As an alternative to the vip-go-mu-plugins repository, [the vip-go-mu-plugins-built repository](https://github.com/Automattic/vip-go-mu-plugins-built)
   can be used for local development. This is a “built” version of VIP MU plugins
   and requires no extra steps.
 * The [VIP Local Development Environment](https://docs.wpvip.com/local-development/use-the-vip-local-development-environment/)
   automatically loads and tracks the staging branch of VIP MU plugins when `--mu-
   plugins=demo` is selected in the environment creation process. No build steps
   are needed for this configuration.

Last updated: September 02, 2025