Yoko Core no longer requires the MCP Adapter plugin. 1.33.0 made it a hard requirement, so on a site without MCP Adapter, Yoko Core showed a missing-plugin notice and could not be reactivated. 1.33.1 removes the requirement. Nothing else changes from 1.33.0.

Yoko Core now tidies the structured data SEOPress generates for events and posts, so Google can read dates, locations, attendance mode and tickets, and a new WP-CLI command shows exactly what a page emits. The soft gate gains two developer hooks: one lets known members past it, the other reacts when someone fills in its form. Yoko Core now requires the MCP Adapter plugin — install it before updating. Three fixes: a renamed standalone SSO plugin no longer crashes wp-admin, ACF's styled selects work again, and testing-walkthrough scenarios no longer vanish.

WordPress core only ever lets a user hold one role at a time. Yoko Core now turns the Role field on the Edit User screen into a multi-select, so a site can give a user more than one role — without installing Members or PublishPress Capabilities, both of which already do this and are deferred to automatically when present. This release also carries several contributor-tooling improvements that had been sitting on develop waiting for real plugin work to ship alongside.

Three features. Card is a new block that works like a Group and can turn the whole card into one accessible link — the image, the padding, the gap between two lines. The Additional CSS box on every block now behaves like Sass: nesting works to any depth, and media queries work where they were silently dropped before. And a theme's own SVG files now appear in the Icon block — drop them in an /icon folder and they are there. A stretched-link fix comes with them.

WordPress sends its password resets and account notices as plain text that could have come from any site on the internet. 1.30.0 adds the option to send them as HTML carrying the site's own logo, colour and fonts, with a new Appearance > Email Branding screen to switch it on and rewrite what the four most visible ones say. It ships off — updating changes nothing an account holder receives until a site opts in. The Login Screen customiser moves to Appearance beside it, and both now inherit the block theme's main colour when no colour is set.

The Primary Term option that 1.29.0 added to the terms block did nothing at all on WordPress 6.7. A block set to render only the primary term rendered every term, with nothing to indicate the setting was being ignored. Sites on 6.8 were unaffected, which is why this went unnoticed. The option is also now two toggles rather than a dropdown, matching the rest of the panel it sits in.

Version 1.29.0 brings two per-post controls to the block editor that only ever existed in the classic one — the primary term picker and the unpublish date — and gives the terms block a primary-term option. Both controls had the same thing wrong with them, and it was worse than their absence: a save in the block editor deleted the value the classic editor had stored.

Clicking a field in the Consolidated Taxonomy Panel before typing anything opened a dropdown with nothing in it, so an editor had to guess at a term name before the field would show them anything. It now lists the whole taxonomy on that first click, most-used terms first. The release zip also drops about a megabyte of npm lockfiles that were never used at runtime.

Version 1.28.1 finishes the job 1.28.0 started. The consolidated Taxonomies panel showed its fields in whatever order the taxonomies happened to be registered in, which meant the field an editor used on every single record could sit at the bottom with no way to move it. Administrators can now order them, from the same picker, saved once for everyone.

Version 1.28.0 gives administrators two ways to fix a document sidebar that has grown unusable. Panels can be dragged into the order editors actually work in, saved once for everyone on the site. And a post type's taxonomies can be collapsed into a single panel of chip fields, chosen in the editor by the person looking at the sidebar they are fixing. Both replace the hand-written nth-child() CSS that sites have been using for this, which silently reorders the wrong panel the moment a conditional panel appears.