Between April 1 and April 15, 2026, WooCommerce 10.7.0 shipped on April 14 with security updates and HPOS sync on read switched off by default, and nginx 1.30.0 became the new stable line with HTTP/1.1 and keep alive as proxy defaults. Stores with custom order code should test WooCommerce 10.7 on staging, and servers that use proxy_pass should test nginx 1.30.0, before updating.
Below is a quick summary table, then a section on the release covering what shipped, what it means for you, how we use it in WordPress builds, what it means for mobile apps and what to do next.
At a glance
| Release | Date | Type | Who should care | Action |
|---|---|---|---|---|
| WooCommerce 10.7 | Apr 14 | Feature and security | Every WooCommerce store, especially HPOS stores with custom order code or REST API order integrations | Update after a staging test |
| nginx 1.30.0 stable | Apr 14 | Major release | Servers using proxy_pass | Test proxy behavior |
WooCommerce 10.7
WooCommerce 10.7 was released on April 14, 2026. It cuts HPOS order REST queries by 51 percent, turns off HPOS sync on read by default, extends the Fulfillments beta and includes security hardening, with minimums still at WordPress 6.8 and PHP 7.4. Test any code that writes order data straight to the posts table before you update.
For the full write up, read our standalone post: WooCommerce 10.7.
nginx 1.30.0 Stable Changes Proxy Defaults to HTTP/1.1 With Keep Alive
What shipped
nginx.org released the 1.30.0 stable branch on April 14, 2026. What it carries over from mainline:
- nginx 1.30.0, the new stable branch, was released April 14, 2026.
- It brings Early Hints, HTTP/2 to backends, Encrypted ClientHello and sticky sessions to the stable branch.
- It includes Multipath TCP support.
- The default proxy_http_version is now 1.1 with keep alive.
What it means for you
This is not a security release, but it needs action. The change in proxy defaults means upstream connections now stay open, which can change how backends behave when moving from 1.28.
How we use it in WordPress builds
Early Hints can let a browser start loading CSS and fonts before WordPress finishes building the page. We test the new proxy default against PHP and cache backends before switching a site to 1.30.
What it means for mobile apps
Keep alive between nginx and backends can cut time on busy REST API endpoints that apps call often. The app does not need an update to benefit.
What to do next
Before moving from 1.28 to 1.30, test any proxy_pass location for behavior with keep alive. Our WordPress security and hosting team can plan the branch move.
How AlphaWeb handles updates for you
WooCommerce 10.7 is a good example of why we stage updates: a default change like sync on read only shows up when real order workflows run. Our support and maintenance plans cover tested WordPress core, theme and plugin updates on staging first, then in production, with uptime monitoring and help when something breaks. Our WordPress security and hosting service keeps PHP versions and servers current, and our custom WordPress development and custom mobile apps teams put new features to work when they fit.
We also track the server, app platform and payment releases behind your site and app, including nginx. Our WordPress security and hosting plans keep servers and databases patched, and our mobile app team handles SDK, policy and store changes for AppPresser and Ionic apps.
Request a custom development quote, or tell us about your project through our Mission Brief.
Frequently asked questions
Is nginx 1.30.0 a security release?
No. It is the new stable branch. It needs testing because proxied requests now use HTTP/1.1 with keep alive by default.
Brief Us on Your Mission
Want to talk about a website, mobile app, migration or AI project? Fill out the Mission Brief and a specialist will follow up to schedule a call and put together a free quote.
