From 4dfce6ee7715b69a1d4f92b1911000e3e69c6a45 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Burak=20Emre=20Kabakc=C4=B1?= <emrekabakci@gmail.com>
Date: Thu, 16 Apr 2026 02:53:58 +0100
Subject: [PATCH] fix(ci): include component in title pattern to fix
 release-please auto-tagging
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

release-please v4's buildRelease checks:
  normalizeComponent(branchName.component) !== normalizeComponent(branchComponent)
and returns early (skips release creation) on mismatch.

branchName.component comes from parsing the merged PR's title.
branchComponent comes from getBranchComponent() which falls through
to getDefaultPackageName() → root package.json name ("lobu-monorepo")
when component/package-name is empty or unset (JS || treats "" as falsy).

Fix: set package-name to "lobu" (controls the expected component) and
include ${component} in the title pattern so the parser can extract it.
Result: titles like "chore(main): release lobu 3.4.4", and the
component check passes ("lobu" === "lobu").

include-component-in-tag remains false, so tags stay as v3.4.4 (no
component suffix).
---
 release-please-config.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/release-please-config.json b/release-please-config.json
index 9dc4fd306..9bb971193 100644
--- a/release-please-config.json
+++ b/release-please-config.json
@@ -9,10 +9,10 @@
   "prerelease": false,
   "separate-pull-requests": false,
   "changelog-path": "CHANGELOG.md",
-  "pull-request-title-pattern": "chore(main): release ${version}",
+  "pull-request-title-pattern": "chore(main): release${component} ${version}",
   "packages": {
     ".": {
-      "component": "",
+      "package-name": "lobu",
       "release-type": "node",
       "extra-files": [
         {