WordPress.org News

https://wordpress.org/news/

ADDED as candidate by the 2026-07-18 weekly quality audit: WordPress core security releases (e.g. 7.0.2 / WP2Shell pre-auth RCE chain, 2026-07-17) had no curated discovery path; the release post is the vendor-primary for core CVEs affecting the huge Swiss/EU public-sector WordPress estate. Low cadence, high signal on security releases; the news feed carries them all. Promote to active after 3 contributing runs. | 2026-07-27 intel run: FIRST successful fetch since being added (rotation priority cleared) via the documented feed https://wordpress.org/news/feed/, ten items spanning 2026-06-06 to 2026-07-22, none in-window. 200-but-quiet: last_successful_fetch set, consecutive_quiet_periods incremented to 1. | 2026-09-29: content check said 'irrelevant' - false positive: feed https://wordpress.org/news/feed/ is healthy (10 items, newest 2026-09-22) and 4 of its 10 items are core security releases (7.1.2 critical RCE fix 2026-09-22, 7.1.1 2026-09-17), but the release excerpts only ever use the words 'security'/'vulnerability' (2 distinct terms < RELEVANCE_MIN 3). Security-only feed also works: https://wordpress.org/news/category/security/feed/ (release posts only, ~1-5 week cadence but a 4-month gap 2026-03-10 -> 2026-07-17, so it would need max_staleness_days >= 120 if adopted); kept the general feed as superset. Recipe unchanged: feed -> extract <release post URL>. Set content_scope general-news (lowers the relevance term floor to 1) so the check stops flagging this narrow-vocabulary feed. (2026-09-29T2134Z-audit) | 2026-09-29: the security-category feed is security by construction but its release excerpts use a narrow vocabulary ("security release", "vulnerability"), so the health check applies the one-term rule (2026-09-29T2134Z-audit)