Following WordPress news is part of running a WordPress site responsibly. Releases bring security fixes, new editor features and occasionally changes that affect your theme or plugins, and knowing what is coming lets you plan updates instead of reacting to them. The challenge is signal versus noise: plenty of sites repackage announcements, and rumors spread faster than release notes. This guide lists the primary sources worth following, explains how the release cycle works, and suggests a simple routine for keeping your site in step.
Start with the official WordPress news sources
The WordPress project publishes its own announcements, and these should always be your first stop. Everything else is commentary on them.
WordPress.org News
The official blog at wordpress.org/news carries release announcements (major, minor and security releases), beta and release candidate calls for testing, and project-wide updates. It is low volume and authoritative. If you follow only one source, make it this one. It has an RSS feed, and the same headlines appear in the “WordPress Events and News” widget on your own dashboard.
Make WordPress blogs
The contributor teams work in the open on make.wordpress.org. Each team has its own blog, and several are useful even if you never contribute:
- Make Core publishes release schedules, meeting notes and, most importantly, developer notes (“dev notes”) explaining technical changes in each release. Before a major release, the team publishes a Field Guide that collects all dev notes in one place. If you build or maintain themes and plugins, read it.
- Make Themes and Make Plugins cover the directory review guidelines and changes affecting theme and plugin authors.
- Make Test posts calls for testing new features, a good way to see what is coming before it ships.
- Make Accessibility, Performance, Polyglots and others track their specialist areas.
The WordPress Developer Blog
The Developer Blog publishes tutorials and explainers on new APIs, block development and theme building, plus a regular roundup of what is new for developers. It sits between the terse dev notes and full documentation, and is the best official source for understanding how to use new features.
Official podcast
The project runs WP Briefing, a short podcast covering project news and upcoming releases, available from wordpress.org and the usual podcast apps.
How the WordPress release cycle works
Understanding the release types tells you how urgently to act on a given piece of WordPress news.
| Release type | Version pattern | What it contains | How to respond |
|---|---|---|---|
| Major | 6.x (e.g. 6.4 to 6.5) | New features, editor changes, API additions, deprecations | Read the Field Guide, test on staging, then update |
| Minor / maintenance | 6.x.y | Bug fixes and regressions from the last major release | Applied automatically on most sites; update promptly |
| Security | 6.x.y | Security fixes, often backported to older branches | Update immediately |
| Beta and RC | 6.x-beta1, 6.x-RC1 | Pre-release builds for testing | Test on a staging site only |
Major releases have historically arrived two or three times a year, though the project adjusts its cadence from time to time, so check the current schedule on Make Core rather than assuming. Each major release follows a predictable path: a feature freeze and Beta 1, several betas, release candidates (with a string freeze for translators), then the final release. That gives you several weeks of warning to test.
Version numbers do not follow semantic versioning: going from 6.9 to 7.0 is just another major release, not a signal of a bigger break than usual.
The Gutenberg plugin
Block editor features are developed in the Gutenberg plugin, which ships new versions frequently, roughly every two weeks. Each core release then bundles a set of Gutenberg versions. Following Gutenberg release posts on Make Core shows you editor and Site Editor changes months before they reach core. Running the plugin on a production site is not recommended, but it is useful on a test site if you build block themes or follow Full Site Editing closely.
Community news sites, newsletters and podcasts
Independent publications add context, opinion and coverage of the wider ecosystem: plugin businesses, hosting, acquisitions and community debates. They are valuable, with a few caveats: the landscape changes, sites start and stop publishing, and commentary is not the same as an official announcement. Before subscribing, check that a source is still actively publishing.
- Community news sites. WP Tavern was for many years the best-known independent WordPress news site; check its recent activity before relying on it. Post Status covers the business side of WordPress for professionals.
- Editor-focused coverage. Gutenberg Times tracks block editor and Site Editor developments closely and hosts the Gutenberg Changelog podcast.
- Weekly newsletters. Several curated newsletters round up WordPress news and tutorials each week. A good newsletter saves you from checking a dozen sites; pick one or two rather than ten.
- Podcasts. Beyond WP Briefing, there are long-running shows on WordPress business, WooCommerce and development. Pick by topic.
- Security advisories. Security companies such as Wordfence and Patchstack publish vulnerability reports and weekly roundups covering plugins and themes. These matter for site owners because most real-world WordPress vulnerabilities are in extensions, not core.
How to judge a WordPress news source
- Does it link to the primary source (a wordpress.org post, a Trac ticket, a GitHub issue)?
- Does it separate reporting from opinion?
- Does it disclose sponsorships and affiliate relationships?
- Does it correct mistakes visibly?
Build a low-effort WordPress news routine
You do not need to read everything. A sensible setup for most site owners and freelancers:
- Use an RSS reader. Subscribe to wordpress.org/news, Make Core and the Developer Blog. RSS is built into WordPress; most feeds are at the site address followed by
/feed/. - Add one newsletter and one security feed. That covers the ecosystem and vulnerabilities without daily reading.
- Follow your vendors. Subscribe to the changelogs or update notices of your theme and key plugins. They will tell you when they have tested against a new WordPress version.
- Put release dates in your calendar. When a major release is scheduled, block time a week or two afterwards to update your sites.
Keeping your site in step with releases
News is only useful if it changes what you do. Here is a practical update policy that fits most sites:
- Minor and security releases: leave automatic background updates on (the default for minor core releases). Check the site afterwards.
- Major releases: back up, update a staging copy first, click through key pages and the editor, then update production. Many site owners wait for the first maintenance release (x.y.1) on complex sites; that is a reasonable trade-off as long as you still apply security releases immediately.
- Plugins and themes: update regularly, prioritizing anything flagged in a security advisory. Remove extensions you no longer use.
- PHP: check Tools → Site Health, which warns when your PHP version is outdated. Upgrade PHP on staging first; it is a common source of plugin breakage.
For a full schedule of recurring tasks, see our WordPress maintenance checklist, and make sure your backups are tested before any major update. Security releases are also a good prompt to review the rest of your setup with our security hardening guide.
If you build themes or plugins
Read the Field Guide for every major release, test your code against the betas, and watch for deprecation notices in your logs with WP_DEBUG enabled on a development site. Changes to theme.json, block supports and editor APIs are where block theme authors most often need to adjust. Our WordPress development overview links to the deeper tutorials.
Frequently asked questions
How do I know which WordPress version I am running?
Go to Dashboard → Updates, or check the “At a Glance” widget. Tools → Site Health → Info also lists the WordPress, PHP and database versions.
Should I update the moment a new version is released?
For security releases, yes. For major releases on important sites, test on staging first; a short delay is fine, but do not fall several versions behind.
Where can I see what is planned for future releases?
Make Core publishes release schedules and planning posts, and the project’s roadmap page on wordpress.org summarizes upcoming priorities.
Key takeaways
- Treat wordpress.org/news and Make Core as the primary WordPress news sources; everything else is commentary.
- Major releases bring features and need testing; minor and security releases should be applied promptly.
- The Field Guide and dev notes are essential reading for theme and plugin developers.
- Add one newsletter and one security advisory feed, and check that community sources are still active.
- Turn news into action: back up, test on staging, update, and keep PHP current.
