Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

WP BrowserUpdate · Version history

WP BrowserUpdate changelog and version history

Latest version
6.0.1
Aug 13, 2026 (2 months ago)
Releases
4
since 2025
In the last year
3
about one every 87 days
Tested up to
WordPress 7.1.4
PHP 7.4 or later

Releases each year

  • 20251 release
  • 20263 releases

20263 releases

  1. WP BrowserUpdate 6.0.1Latest

    • Fixed:
    • Corrects the original plugin source strings to en-US so WordPress.org translations can provide locale-specific variants such as en-GB.

  2. WP BrowserUpdate 6.0.0

    • Breaking:
    • Requires WordPress 6.0 or newer.
    • Replaces the legacy space-separated settings storage with the structured wp_browserupdate_options option.
    • Migrates existing wp_browserupdate_browsers, wp_browserupdate_js, and wp_browserupdate_css_buorg values automatically.
    • Removes the old normal-render-path conversion of negative browser versions; values are now passed predictably to the bundled runtime.
    • Removes developer callback settings from the admin UI and saved settings model.
    • Added:
    • Adds interface coverage for the browser-update.org customization options used by WP BrowserUpdate: all runtime browser keys, reminderClosed, notify_esr, noclose, no_permanent_hide, container, url, url_permanent_hide, burl, fixed language, and text overrides.
    • Changed:
    • Takes the long-postponed step of making the browser-update.org integration CSP-compatible by shipping the complete runtime with the plugin, so sites on shared hosting or strict Content Security Policies no longer need to allow scripts from browser-update.org.
    • Adds the required browser-update.org runtime/adapter asset files intentionally, with upstream source URLs and hashes documented for attribution and review.
    • Loads bundled browser-update.org runtime files from the plugin directory through the WordPress script queue.
    • Removes browser-update.org runtime requests from the frontend by loading only same-origin plugin assets.
    • Uses WP BrowserUpdate CSP adapter files for the notification and test-mode scripts so the runtime can avoid generated inline styles.
    • Moves the frontend browser-update.org configuration and notification styles to local, enqueueable assets for better compatibility with stricter Content Security Policies.
    • Uses the WordPress HTTP API with a host allowlist for remote browser-version checks.
    • Uses the WordPress Settings API for the admin settings page.
    • Splits admin settings handling into smaller validation, migration and rendering steps.
    • Documents the bundled browser-update.org runtime, local frontend loading, and expected visitor-facing behavior.
    • Passes dotted browser versions such as 137.0.3912.63 to the bundled runtime without reducing them to major versions.
    • Adds separate Microsoft Edge and Microsoft Internet Explorer thresholds.
    • Ships only the loaded runtime/adapter files in the release package; upstream reference copies are documented by URL and hash rather than duplicated in the plugin ZIP.
    • Security:
    • Adds stricter settings validation before saving options.
    • Sanitizes custom CSS before saving and before frontend output.
    • Hardens external admin links with rel="noopener noreferrer".

  3. WP BrowserUpdate 5.1.1

    • Added:
    • Support for free-text input of browser versions (replaces dropdown selection)
    • Browser version check and caching
    • Cache duration filter: Added a wpbu_browser_version_cache_hours filter to allow developers to adjust the browser version cache duration (default: 6 hours).
    • Changed:
    • Admin settings page follows WordPress admin standards
    • Cleaner field structure: Improved markup and consistency of settings form fields
    • Security: Improved sanitization and nonce handling for all settings fields
    • Performance: Fewer unnecessary remote lookups when opening the admin settings page
    • Fixed:
    • Prevented a frontend “Uncaught Error” caused by invalid/unexpected browser version strings by hardening version parsing and normalization. Thanks to @danyloliptuha for pointing out.

20251 release

  1. WP BrowserUpdate 4.8.1

    • Optimized code.
    • Fixed bug.
    • Updated outdated browser versions.

Questions about WP BrowserUpdate’s releases

What is the latest version of WP BrowserUpdate?

6.0.1, released on Aug 13, 2026 (2 months ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.

How often is WP BrowserUpdate updated?

3 releases in the last year, about one every 87 days. Its first release on WordPress.org dates from April 2025.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in WP BrowserUpdate’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.