Skip to content

Zorderz 1.7.2 — upgrade-path fix and version/config congruence

Choose a tag to compare

@CarletonTorpin CarletonTorpin released this 25 Aug 16:24
· 6 commits to main since this release
f1e8c56

Zorderz v1.7.2 — upgrade-path fix and version/config congruence

A point release over v1.7.1. It repairs the in-place upgrade path for the apps bundle and closes three version and configuration congruence gaps found in review. No database, schema, or REST changes — a straight upgrade over 1.7.1.

Install / upgrade

Zorderz ships as two artifacts that upgrade together. Install or upgrade the theme first, then the apps — the ordering matters and is not enforced by WordPress.

  1. zorderz-theme-1.7.2.zip — the platform kernel and Core services
  2. zorderz-apps-1.7.2.zip — the 19-app bundle

Fixed

  • In-place apps upgrade skipped its re-activation step. The apps bundle re-runs every app's activation on plugins_loaded when its version changes, because uploading a new apps zip over an existing install does not fire WordPress activation. The version marker ZDZ_APPS_VERSION had been left at 1.6.1 since that release, so on a 1.6.1 → 1.7.x in-place upgrade the marker still matched the stored value and the re-activation was silently skipped. ZDZ_APPS_VERSION now derives from the plugin's own Version: header, so it tracks every release and cannot drift again. Fresh installs were never affected (they run activation directly), and per-app database migrations were never affected (each guards itself on its own DB version).

Changed

  • Declared PHP floor aligned to 8.0 everywhere (composer.json and both phpcs rulesets), to match the theme and apps Requires PHP: 8.0 headers.
  • SECURITY.md supported-versions note corrected (Zorderz is past 1.0, not "pre-1.x").
  • Apps bundle and theme move to 1.7.2 in lockstep.

Notes

  • Full CI is required green on this release before merge (the standing bar).
  • For everything the 1.7 line adds — Flow, Projects, Dot Plot, the update-estimate path, schedule inference, and the 502 fix — see the v1.7.0 release notes.