chore: release 1.2.0

[soulevilx]

What changed

• Promotes the content-template extraction changelog notes from Unreleased to 1.2.0.
• Releases the SDK-core cleanup that removes non-native content template features from jooservices/wordpress-sdk.
• Keeps PostBuilder and ContentBuilder documented as generic SDK-safe helpers for WordPress post payloads and Gutenberg block markup.

Why 1.2.0

This is a product release for the SDK boundary change: content templates are not native WordPress REST API SDK features, so they are extracted out of core and users are directed to jooservices/wordpress-content-templates.

Migration notes

• Removed PostsService::createFromTemplate().
• Removed SDK-core story/product-review/content template classes, registry, docs, examples, and template-specific tests.
• Install jooservices/wordpress-content-templates for extracted content templates:

composer require jooservices/wordpress-content-templates

• Generate a payload with that package and publish through the SDK:

$post = $wordpress->posts()->create($template->toPostData());

Validation

Release branch validation run locally:

• composer validate --strict passed.
• composer lint passed.
• composer test passed: 178 tests, 612 assertions.
• composer security passed: no advisories.
• composer quality passed.
• composer test:coverage passed: 97.0% statements, no zero-covered files/classes/methods.
• composer test:coverage-map passed: 101/110 production classes mapped for unit tests, 34 service classes mapped for integration tests, 353 public methods reflected.
• composer test:integration completed with 40 skipped tests because no disposable local WordPress test site is configured in this environment.
• Example syntax validation is not applicable because no SDK examples directory remains after template extraction.

Docker/WP note: stale Docker/WP Composer aliases were removed before merging PR #6 because their docker/wordpress runner files are not present in the repository. No broken Docker/WP scripts remain in Composer for this release.

Risk / BC notes

• This release removes public SDK APIs/classes related to content templates. It is a backward-compatible boundary cleanup only for native WordPress REST API SDK behavior; template users must migrate to the new package.
• Native REST API services, auth, DTOs, pagination, request/response handling, errors, endpoint services, and generic helpers remain covered by validation.

Merge requirement

Do not merge this PR unless required GitHub checks pass, review status is acceptable, no unresolved review/change-request threads remain, and the release branch remains mergeable into master.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cf344bc7-105c-4a57-a93f-0c5b159affd1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/1.2.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}