feat(LINCHPIN-5363): Restore wp-plugin and wp-theme commit types

[surrealwebs]

Task: LINCHPIN-5363

⚠️ Depends on linchpin/commitlint-config#10. Do not merge this before that PR lands and a new version of @linchpinagency/commitlint-config publishes — every commit this preset generates for a WordPress plugin/theme update would fail commitlint until then.

This is stacked on #14 (fix/LINCHPIN-5363/restore-project-wordpress-prefixes) — the diff below is only the incremental change on top of it, and the base branch for this PR is that branch, not main.

Overview

#14 fixed the 6 WordPress plugin/theme rules by switching them to update(wp-plugin): / update(wp-theme):, because that was the only type+scope combination the currently published @linchpinagency/commitlint-config accepted. That was always meant to be interim — update/build land in generic changelog sections, not the dedicated "WordPress Plugins 🔌" / "WordPress Themes 🖌️" sections release-please-config.json already defines for the wp-plugin/wp-theme type.

Once commitlint-config#10 publishes, this PR switches those same 6 rules back to the type form they were always meant to use:

Rule	#14 (interim)	This PR
Themes (major/minor)	update(wp-theme): WordPress	wp-theme(deps): WordPress
Plugins wordpress.org (major/minor)	update(wp-plugin): WordPress wporg	wp-plugin(wporg): WordPress
Plugins packagist.linchpin.com (major/minor)	update(wp-plugin): WordPress linchpin	wp-plugin(linchpin): WordPress

The wporg/linchpin source label moves back into the scope ((wporg), (linchpin)), which is where it lived before #14's workaround and is what commitlint-config#10 adds scopes for.

A judgment call worth flagging

I dropped the duplicate wporg/linchpin word from the subject that #14 added there as a workaround for not having those as valid scopes yet. Keeping it would read as wp-plugin(wporg): WordPress wporg Update dependency ... — the same word twice in one line for no reason, now that the scope carries it again. I kept WordPress in the subject, since that's the distinction you originally asked to have back and it's independent of which type/scope form carries the wporg/linchpin split. If you'd rather keep the wporg/linchpin subject word too for belt-and-suspenders redundancy, easy to add back — just say so.

Verification

Same three checks as #14, run against a local copy of commitlint-config with #10's change applied (since the published package doesn't have it yet):

• jq empty default.json — valid strict JSON.
• npx --package renovate@44 renovate-config-validator --no-global default.json automerge.json — passes.
• Every rendered header and commitBody line in default.json run through the patched explain() — all 38 checks pass.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates the Renovate preset’s WordPress plugin/theme packageRules to restore wp-plugin and wp-theme as commit types (with deps/wporg/linchpin as scopes), aligning generated commit headers with the dedicated changelog sections those types map to (once the corresponding commitlint config update is published).

Changes:

• Switched WordPress theme rules back from update(wp-theme): ... to wp-theme(deps): ... in both commitMessagePrefix and rendered commitBody lines.
• Switched WordPress plugin rules back from update(wp-plugin): ... to wp-plugin(wporg|linchpin): ..., moving the source label back into scope.

Suppressed comments (3)

default.json:510

• The Handlebars expression extracts the “name” by splitting depName on "-" and taking index 1. For Composer packages like "linchpin/some-theme" or "wpackagist-plugin/akismet", this renders incorrect/empty values (e.g., "theme" or "plugin/akismet"). Splitting on "/" first yields the actual package name reliably across all matched vendors.

      "commitBody": "{{#each upgrades as |upgrade|}}wp-theme(deps): {{replace '-' ' ' (lookup (split depName '-') 1 ) }} from {{{upgrade.currentValue}}} to {{{upgrade.newValue}}}\n{{/each}}"

default.json:574

• The Handlebars expression extracts the “name” by splitting depName on "-" and taking index 1. For Composer packages like "linchpin/some-plugin" or "wpackagist-plugin/akismet", this renders incorrect/empty values (e.g., "plugin" or "plugin/akismet"). Splitting on "/" first yields the actual package name reliably across all matched vendors.

      "commitBody": "{{#each upgrades as |upgrade|}}wp-plugin(wporg): {{replace '-' ' ' (lookup (split depName '-') 1 ) }} from {{{upgrade.currentValue}}} to {{{upgrade.newValue}}}\n{{/each}}"

default.json:638

• The Handlebars expression extracts the “name” by splitting depName on "-" and taking index 1. For Composer packages like "linchpin/some-plugin" this can render only the tail segment (or empty) instead of the full package name. Splitting on "/" first yields the actual package name reliably across all matched vendors.

      "commitBody": "{{#each upgrades as |upgrade|}}wp-plugin(linchpin): {{replace '-' ' ' (lookup (split depName '-') 1 ) }} from {{{upgrade.currentValue}}} to {{{upgrade.newValue}}}\n{{/each}}"

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.