Skip to main content

How We Release Plugin Updates

Updated this week

Keeping our plugins stable, secure, and continuously improving requires a well-defined release process. This article explains how we deliver updates, what you may experience when a new version is released, and why some updates may not be immediately available to everyone via the WordPress updater.

We use two main strategies to release plugin updates.

Instant Release

In an instant release, the new version becomes immediately available to all users through the WordPress update system as soon as it is published. This approach is typically used for:

  • Minor improvements

  • Updates with a very low risk of compatibility issues

When an instant release is performed, all sites will see the update at the same time.

Gradual Rollout

In many cases, we adopt a gradual rollout strategy. With this approach, the update is distributed progressively over a defined period of time, which can span several hours.

You may occasionally see a timeframe mentioned (for example, 24 hours), but this is not a fixed rule. The actual duration of a rollout can vary depending on the nature of the update and ongoing monitoring results.

During a gradual rollout:

  • Some sites receive the update earlier than others

  • The update becomes available to increasing percentages of users over time

  • The rollout can be slowed down, paused, or stopped if unexpected issues are detected

Why We Use Gradual Rollouts

Gradual rollouts are a standard practice in modern software delivery and are widely adopted across the software industry, from SaaS platforms to operating systems and large-scale web applications.

This approach allows teams to release updates in a controlled and observable way, rather than exposing all users to potential risks at once.

Key benefits include:

  • Early issue detection: if an edge case or unexpected conflict emerges, it can be identified before affecting all users

  • Risk mitigation: potential problems are limited to a smaller subset of installations

  • Improved stability: critical fixes or adjustments can be made quickly without requiring a global rollback

  • Better compatibility assurance: real-world usage provides valuable feedback beyond internal testing

This process helps ensure that updates are safe and stable for the majority of users before being fully released.

Website Downloads vs WordPress Updates

It is important to understand the difference between downloading the plugin from our website and updating it through WordPress.

  • Website downloads always provide the latest fully released version of the plugin

  • WordPress updates may be subject to a gradual rollout

This means that if a new version has been announced but is not yet visible in your WordPress dashboard, the rollout may still be in progress. In this case, your site will receive the update automatically once it reaches your rollout group.

What You Should Do

In most cases, no action is required on your part.

  • If you see the update available, it is safe to install

  • If you do not see it yet, it will appear automatically once the rollout completes

  • If you prefer immediate access, you can always download the latest version directly from our website

We strongly recommend keeping automatic updates disabled on staging or critical production environments and testing updates thoroughly before deploying them live.

Did this answer your question?