Skip to content

Release 4.14.0 - #130

Merged
jasperf merged 1 commit into
mainfrom
release/4.14.0
Nov 18, 2026
Merged

jasperf merged 1 commit into
mainfrom
release/4.14.0

Conversation

@jasperf

@jasperf jasperf commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

What this does

Releases 4.14.0 — the four merged PRs since v4.13.0 (11/15/26): the new default homepage (#126), the section rhythm contract (#127), vertical block style gating (#128), and the directory copy pass (#129). The bundled legal patterns stay registered (removal is deferred to 5.0.0), so this is a minor bump, not the major one.

Version bumps (all in sync)

  • style.css — Version: 4.14.0
  • readme.txt — Stable tag: 4.14.0 and a new = 4.14.0 - 11/18/26 = changelog section (ADDED/CHANGED prefixes, matching the Moiraine format)
  • package.json — version 4.12.0 (stale two releases) to 4.14.0
  • CHANGELOG.md — the ## [Unreleased] section becomes ## [4.14.0] - 2026-11-18; no entries left under Unreleased

composer.json has no version field, so there is nothing to bump there. The other 4.13.0 strings in the tree are the intentional "Deprecated in 4.13.0" markers on the legal patterns and styles/legal-blue.json, which stay as they are.

Verification

  • git diff origin/main reviewed: only the four version/changelog files, 12 insertions, 4 deletions.
  • grep -rn '4\.13\.0' across the tree confirms no stale version references outside the changelog history and the deprecation markers.
  • No pattern, template, or PHP changes, so the four-pass validation is unaffected.

Reviewer notes

  • The readme.txt changelog entry is a condensed version of the CHANGELOG.md 4.14.0 section; the full detail lives in CHANGELOG.md as the readme points out for older releases.
  • After merge: tag v4.14.0 on the merge commit so create-release.yml builds the release zip, then watch for the auto draft on WordPress.org.

@jasperf
jasperf merged commit d530e18 into main Nov 18, 2026
3 checks passed
@jasperf
jasperf deleted the release/4.14.0 branch November 18, 2026 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant