Commit 19b0d050c7 for wordpress.org

commit 19b0d050c7118fa69c2d6a9c066a30321841099e
Author: westonruter <westonruter@git.wordpress.org>
Date:   Sat Sep 26 19:26:45 2026 +0000

    Build/Test Tools: Allow far-future caching in the local environment.

    Add an `expires` directive for CSS, JavaScript, font and image files to the nginx config template used by the local Docker environment, so that static asset caching can match normal production behavior. Without it, static files are served with only `Last-Modified` and `ETag`, so browsers fall back to a heuristic lifetime of a tenth of each file's age, which in a freshly built checkout is seconds to minutes. Caching then depends on how recently the assets were built, and comparisons with script and style concatenation are skewed, since `load-scripts.php` and `load-styles.php` already send a one-year lifetime of their own.

    The lifetime is controlled by a new `LOCAL_NGINX_STATIC_EXPIRES` option, and it defaults to `off` so that it is opt-in: with most core assets versioned by the WordPress version rather than by their content, a far-future lifetime serves edited files stale until a hard reload. A missing file still falls through to WordPress, so a virtual asset such as the dynamic `/favicon.ico` keeps working.

    Developed in https://github.com/WordPress/wordpress-develop/pull/13777.
    Follow-up to r63308.

    See #57548, #65634.
    Fixes #66194.

    Built from https://develop.svn.wordpress.org/trunk@63946


    git-svn-id: http://core.svn.wordpress.org/trunk@63112 1a063a9b-81f0-0310-95a4-ce76da25c4cd

diff --git a/wp-includes/version.php b/wp-includes/version.php
index be2cd2bafe..2c97846ee9 100644
--- a/wp-includes/version.php
+++ b/wp-includes/version.php
@@ -16,7 +16,7 @@
  *
  * @global string $wp_version
  */
-$wp_version = '7.2-alpha-63945';
+$wp_version = '7.2-alpha-63946';

 /**
  * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.