Skip to main content

1.31.1 - Nothing changes on your site; the tooling that builds it changes a lot

· 2 min read
Konstantin Brazhnik
Senior Full Stack Engineer @ Yoko Co

This release changes nothing a visitor or an editor can see. No plugin code was touched between 1.31.0 and 1.31.1 — every change in this cycle is to the tooling and instructions the people and agents working on Yoko Core use. It goes out as a version so that main and develop stay in step and the next real release starts from a clean base. Updating a site to it is safe and does nothing.

  • [IMPROVEMENT] Every feature now gets a structured code review before its pull request is opened. The new ce-code-review skill picks reviewer personas from what the diff actually touches — the two content-protection gates, block and Beaver Builder surfaces, REST permission callbacks, the docs and Playground demo every user-visible change owes — and returns findings with severity and evidence rather than impressions. The method is fetched from Every's published guide on each run, so it stays current without a stale copy living here.
  • [BUG FIX] The Docker dev site builds again in a cloud session. Its image fetched apt packages over plain HTTP, which the egress proxy refuses, so the build died at apt-get update before it installed a single package. It now fetches over HTTPS and trusts the interception CA, both no-ops on a normal machine.
  • [BUG FIX] npm run lint:js and npm run lint:css finish. With no ignore file in the repo, both linted the composer vendor tree, the webpack output and the 2.3 MB pdf.js bundle. The CSS lint went from never returning to four seconds.
  • [IMPROVEMENT] The cloud-session setup notes now name the two egress entries that are easy to get subtly wrong — wordpress.org is not covered by a *.wordpress.org wildcard, and an allowlist change does not reach containers until a new session — and record that Composer needs COMPOSER_ALLOW_SUPERUSER=1 as root or it silently skips registering the WordPress coding standards.
  • [IMPROVEMENT] The release rules keep the one fact worth repeating: merging the release candidate ships nothing, the tag does. 1.29.0 reached main untagged and was never offered to a single site.