You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ All notable changes to the WordPress Operations Runbook template.
12
12
- Added Learn WordPress's [Writing in the WordPress voice](https://learn.wordpress.org/course/writing-in-the-wordpress-voice/) as the recommended WordPress-specific voice and accessibility reference when runbook material is adapted into user-facing or cross-team communications.
13
13
14
14
### Changed
15
+
- Made the generated-artifact validator read the expected version string from the Markdown frontmatter instead of hardcoding `Version 3.1`, preventing future publish-flow failures after routine version bumps.
15
16
- Updated Section 1.4 of the canonical runbook so the in-document version history matches the actual template release history (`3.1`, `3.0.1`, `3.0`, `2.0`) instead of stale placeholder entries.
16
17
- Separated Playwright PDF visual validation from the artifact publish path so `generate-docs.yml` can publish after artifact checks while the dedicated visual workflow handles layout regression checks on workflow, packaging, and Pandoc changes.
17
18
- Aligned more of the operational procedures with the current runbook-skill safety rules by normalizing the cache-plugin annotation string, correcting the remaining singular `--field` WP-CLI examples to explicit `--fields=... --format=csv` pipelines, and adding approval/warning markers around additional side-effect commands (`wp db query` migrations, cache flushes, imports, option updates, transient deletion, and `wp eval-file` test mail).
0 commit comments