The second half of August 2026 brought WordPress 7.1, a major release with responsive styles, a new media editor and a fully iframed post editor. On the AI side, xAI connected Grok Bot to X so a Bot can search posts, read a timeline and check mentions. For apps, Ionic Framework 9 shipped, Sign in with Apple moved new relay addresses to private.icloud.com, Google Play began requiring Android 16 targeting, and Angular published SSR security advisories. Here is what shipped and what it means for your website and app.
What shipped at a glance
| Release | Date | Type | Action |
|---|---|---|---|
| WordPress 7.1 "Mary Lou" | August 19, 2026 | Major release | Plan and test |
| Angular security advisories | August 18, 2026 to Aug 27 | Security | Update Angular packages |
| Ionic Framework 9 | August 19, 2026 | Major release | Run the migration tool |
| Sign in with Apple relay domain | August 24, 2026 | Requirement | Allow the new domain |
| Grok Bot on X (xAI) | August 29, 2026 | AI product | Watch |
| Target API level 36 deadline | August 31, 2026 | Deadline | Target API 36 |
WordPress 7.1 "Mary Lou"
WordPress 7.1, code named "Mary Lou", was released on August 19, 2026, with responsive styles by screen size, a new media editor, richer Notes and a post editor that is fully iframed for all themes. It also adds native AVIF, HEIC and HDR gain map support and handles image processing in the browser. Test custom plugins, meta boxes and editor scripts on staging before you update.
For the full write up, read our standalone post: WordPress 7.1: Responsive Styles, a New Media Editor and Richer Notes.
Angular security advisories
What shipped
The Angular team published these security advisories in this period:
- CVE-2026-88057 (medium, August 18) and CVE-2026-88059 (medium, August 20)
- CVE-2026-88056 (high, August 27): SSRF and credential disclosure in SSR
- CVE-2026-88058 and CVE-2026-88060 (high, August 27): SSR XSS
What it means for you
These flaws are in the Angular framework, not in WordPress. They matter if you run an Angular front end, an Ionic Angular app or server side rendering in front of WordPress.
How we use it in WordPress builds
On headless WordPress front ends built with Angular, we update the @angular packages to the fixed version for the project's major line and rerun rendering, login and form tests.
What it means for mobile apps
Ionic Angular apps ship Angular inside the app, so a fix for code that runs in the app needs a rebuild and a new store submission.
What to do next
- Update platform-server to Angular 22.1.4, 21.2.22 or 20.3.30 or later.
- Ask our mobile app team to rebuild and resubmit an affected app.
Ionic Framework 9 Supports Angular 22, React Router 6 and Vue Router 5
What shipped
Ionic released Framework 9 on August 19, 2026. The main changes:
- Ionic announced Ionic Framework 9 on August 19, 2026.
- It supports Angular 18 through 22 and defaults to zoneless change detection.
- It adds React Router 6 and Vue Router 5 support, and the React output target now requires React 18 or later.
- @ionic/angular/standalone becomes @ionic/angular, and lazy imports move to @ionic/angular/lazy.
- A migration tool runs with npx @ionic/migrate.
What it means for you
Ionic 9 changes import paths and raises minimum framework versions. Apps need a planned migration.
How we use it in WordPress builds
The REST API calls an Ionic app makes to WordPress do not change between Ionic 8 and 9, so the site needs no edits for this upgrade.
What it means for mobile apps
AppPresser apps use Ionic components, so this is a major upgrade for app UI code. The migration tool handles most import changes, then each screen needs testing.
What to do next
Run the migration tool on a branch and test every screen. Our custom mobile app team schedules Ionic upgrades with Capacitor updates.
Sign in with Apple Moves New Relay Addresses to private.icloud.com
What shipped
Apple updated its Sign in with Apple domain plans on August 24, 2026:
- On August 24, 2026, Apple said new Sign in with Apple addresses will be issued on private.icloud.com, starting later in 2026.
- They were previously issued on privaterelay.appleid.com, and existing addresses there continue to work.
- iCloud+ Hide My Email addresses will remain on icloud.com.
- Developers should make account systems, email validation and allowlists accept the new domain.
What it means for you
If your site or app checks email domains, new Apple users could be blocked at sign up until private.icloud.com is allowed.
How we use it in WordPress builds
Sign in with Apple plugins create WordPress users with the relay address. We check email validation, spam filters and mail settings so the new domain works.
What it means for mobile apps
AppPresser apps that offer Sign in with Apple create WordPress accounts through the API. We test sign up with the new domain.
What to do next
Search your code and plugin settings for privaterelay.appleid.com and add private.icloud.com. Our custom WordPress development team can do it.
Grok Bot on X from xAI
What shipped
On August 29, 2026, xAI gave Grok Bot a tighter integration with X. The X connector links a Grok Bot account to an X account, creating an X developer account if you do not have one, and paid Grok Bot users get free X API credits to start. A Bot can search posts on X, read your timeline, check your mentions and pull together what is happening around a topic. A separate X plugin covers searching posts, reading timelines, pulling trends and managing bookmarks. xAI called it the first version of the integration.
What it means for you
Social listening, such as tracking mentions of your brand or a topic, can be handed to a Bot instead of checked by hand.
How we use it in WordPress builds
With Grok Bot, a Bot can summarize what people are saying about a topic on X and draft blog or newsletter ideas for review in WordPress. Anything published still goes through a person.
What it means for mobile apps
A Bot can watch mentions of an AppPresser app on X and summarize feedback for the team.
What to do next
- Pick one topic or brand name for a Bot to track and review its summaries weekly.
- Learn more about Grok.
Google Play Requires Android 16 Targeting for New Apps and Updates From August 31, 2026
What shipped
Google Play's target API requirement for 2026 took effect on August 31, 2026:
- Starting August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher.
- Existing apps must target Android 15 (API level 35) or higher to stay available to new users on newer Android versions.
- Developers can request an extension to November 1, 2026.
- Wear OS and Android Automotive OS apps must target API 35; Android TV and Android XR apps must target API 34.
What it means for you
An Android app update cannot be published unless it targets API 36. Older apps that are not updated lose visibility to new users on newer phones.
How we use it in WordPress builds
The target API level is a setting in the Android build. WordPress plugins, themes and the REST API are untouched by it.
What it means for mobile apps
Every AppPresser Android build after August 31 must target API 36. We test behavior changes from Android 16 before each release.
What to do next
If you missed the deadline, request the extension in Play Console and schedule a build. Our custom mobile app team handles Play updates.
How AlphaWeb handles updates for you
We follow WordPress, WooCommerce, PHP and the major releases from xAI, Anthropic and OpenAI, test each update on staging and apply it on your schedule. Hosting and server changes are covered by our WordPress security and hosting service.
We also track the server, app platform and payment releases behind your site and app, including Angular, Ionic, App Store and Google Play. 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.
Frequently asked questions
Do I need an X developer account for Grok Bot?
No. If you do not have one, it is created for you when you connect the X connector.
Do existing Sign in with Apple users need to do anything?
No. Existing privaterelay.appleid.com addresses keep working. The change only affects new addresses, so sites and apps just need to accept private.icloud.com.
Brief us on your mission
Planning your move to WordPress 7.1 or a new build that uses it? Tell us about your project and a specialist will follow up.
