WordPress Release News

Most WordPress release coverage is a rewrite of the official announcement published the same afternoon. That tells you what the release notes already said. It does not tell you whether the update will break the custom blocks on a client site, or which of the thirty sites you maintain should go first.

The coverage here is written from the position of having to actually ship these updates across a client portfolio. Each release post answers the same three questions: what actually changed (not the marketing framing), what breaks in real setups — custom blocks, page builders, editor plugins, theme CSS — and what to test, with enough specificity to hand the list to somebody else.

Release cycles get covered as they happen rather than only at the end. A major WordPress version moves through beta, several release candidates, and then final over roughly six weeks, and the useful moment to find out that your custom block breaks is during beta — not on release day when the client's editor stops loading. Posts published during a cycle are dated and stay up afterwards, because the "what broke in 7.1" question keeps getting asked for months after 7.1 ships.

What this section does not do is chase every point release. Security and maintenance releases get covered when there is something to act on — an actively exploited vulnerability, a regression worth waiting out — and skipped when the honest advice is just "let auto-updates handle it." Vulnerability disclosures live in Security rather than here, since those stay useful as remediation references long after they stop being news.