fix: use conventional release pr titles

Author: pedronauck

.github/workflows/release.yml

@@ -69,8 +69,7 @@ jobs:
     if: |
       (github.event_name == 'push' &&
        github.ref == 'refs/heads/main' &&
-       !startsWith(github.event.head_commit.message, 'release:') &&
-       !startsWith(github.event.head_commit.message, 'ci(release):') &&
+       !startsWith(github.event.head_commit.message, 'build: release ') &&
        !startsWith(github.event.head_commit.message, 'Merge pull request') &&
        github.event.head_commit.author.name != 'github-actions[bot]') ||
       (github.event_name == 'workflow_dispatch' &&
@@ -156,8 +155,7 @@ jobs:
       (
         github.event_name == 'pull_request' &&
         (
-          startsWith(github.event.pull_request.title, 'release: Release ') ||
-          startsWith(github.event.pull_request.title, 'ci(release): Release ')
+          startsWith(github.event.pull_request.title, 'build: release ')
         )
       ) ||
       (
@@ -206,8 +204,7 @@ jobs:
       github.event_name == 'push' &&
       github.ref == 'refs/heads/main' &&
       (
-        startsWith(github.event.head_commit.message, 'release:') ||
-        startsWith(github.event.head_commit.message, 'ci(release):')
+        startsWith(github.event.head_commit.message, 'build: release ')
       )
     runs-on: ubuntu-latest
     timeout-minutes: 120
@@ -254,7 +251,7 @@ jobs:
           else
             echo "Could not get version from git-cliff. Got: $VERSION"
             echo "Fallback: Extract from commit message"
-            VERSION=$(git log -1 --pretty=format:"%s" | sed -E 's/.*Release v([0-9]+\.[0-9]+\.[0-9]+).*/\1/')
+            VERSION=$(git log -1 --pretty=format:"%s" | sed -E 's/.*release v([0-9]+\.[0-9]+\.[0-9]+).*/\1/')
             if [[ "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
               git config user.name "github-actions[bot]"
               git config user.email "github-actions[bot]@users.noreply.github.com"

internal/orchestrator/pr_release.go

@@ -359,7 +359,7 @@ func (o *PRReleaseOrchestrator) commitChanges(ctx context.Context, version strin
 		}
 	}
 	// Commit if there are changes
-	message := fmt.Sprintf("release: prepare release %s", version)
+	message := fmt.Sprintf("build: prepare release %s", version)
 	return o.gitRepo.Commit(ctx, message)
 }
 
@@ -470,7 +470,7 @@ func (o *PRReleaseOrchestrator) createPullRequest(
 }
 
 func releasePullRequestTitle(version string) string {
-	return fmt.Sprintf("release: release %s", version)
+	return fmt.Sprintf("build: release %s", version)
 }
 
 // executeWithSaga runs the workflow with saga-based rollback support

internal/orchestrator/pr_release_test.go

@@ -352,9 +352,9 @@ func TestPRReleaseOrchestrator_Execute(t *testing.T) {
 		gitRepo.On("AddFiles", mock.Anything, "package.json").Return(nil).Once()
 		gitRepo.On("AddFiles", mock.Anything, "package-lock.json").Return(nil).Once()
 		// tools/* updates removed
-		gitRepo.On("Commit", mock.Anything, "release: prepare release v1.1.0").Return(nil).Once()
+		gitRepo.On("Commit", mock.Anything, "build: prepare release v1.1.0").Return(nil).Once()
 		gitRepo.On("PushBranch", mock.Anything, branchName).Return(nil).Once()
-		githubRepo.On("CreateOrUpdatePR", mock.Anything, branchName, "main", "release: release v1.1.0",
+		githubRepo.On("CreateOrUpdatePR", mock.Anything, branchName, "main", "build: release v1.1.0",
 			mock.MatchedBy(func(body string) bool {
 				return strings.Contains(body, "Release v1.1.0") && strings.Contains(body, "### Features")
 			}),
@@ -433,7 +433,7 @@ func TestPRReleaseOrchestrator_Execute(t *testing.T) {
 			mock.Anything,
 			branchName,
 			"main",
-			"release: release v1.1.0",
+			"build: release v1.1.0",
 			mock.MatchedBy(func(body string) bool {
 				return strings.Contains(body, "Release v1.1.0") && strings.Contains(body, "### Fixes")
 			}),
@@ -1344,7 +1344,7 @@ func TestPRReleaseOrchestrator_commitChanges(t *testing.T) {
 		gitRepo.On("AddFiles", ctx, "package.json").Return(nil).Once()
 		gitRepo.On("AddFiles", ctx, "package-lock.json").Return(nil).Once()
 		// no tools files added
-		gitRepo.On("Commit", ctx, "release: prepare release v1.2.0").Return(nil).Once()
+		gitRepo.On("Commit", ctx, "build: prepare release v1.2.0").Return(nil).Once()
 
 		orch := NewPRReleaseOrchestrator(gitRepo, githubRepo, fsRepo, cliffSvc, npmSvc)
 

skills/releasepr/SKILL.md

@@ -101,9 +101,8 @@ Conventional-commit prefixes drive the version bump — wrong prefixes mean wron
 versions or "no changes":
 
 - `fix:` → patch · `feat:` → minor · `feat!:` / `BREAKING CHANGE:` → major.
-- A commit subject starting with `release:` or `ci(release):` merged to the
-  default branch is what triggers the **production release** — do not hand-write
-  such commits.
+- A commit subject starting with `build: release ` merged to the default branch
+  triggers the **production release** — reserve it for generated release PRs.
 - Bot commits and `Merge pull request` commits are skipped by the release-PR job.
 
 **STOP. Read `references/release-notes.md` and `references/release-workflow.md`

skills/releasepr/assets/release.yml.template

@@ -46,8 +46,7 @@ jobs:
     if: |
       (github.event_name == 'push' &&
        github.ref == 'refs/heads/main' &&
-       !startsWith(github.event.head_commit.message, 'release:') &&
-       !startsWith(github.event.head_commit.message, 'ci(release):') &&
+       !startsWith(github.event.head_commit.message, 'build: release ') &&
        !startsWith(github.event.head_commit.message, 'Merge pull request') &&
        github.event.head_commit.author.name != 'github-actions[bot]') ||
       (github.event_name == 'workflow_dispatch' &&
@@ -77,13 +76,12 @@ jobs:
           INITIAL_VERSION: ${{ env.INITIAL_VERSION }}
         run: go run "${{ env.PR_RELEASE_MODULE }}" pr-release --force --enable-rollback --ci-output
 
-  # Validate the release PR (title starts with "release: release ").
+  # Validate the release PR (title starts with "build: release ").
   dry-run:
     name: Dry-Run Release Check
     if: |
       (github.event_name == 'pull_request' &&
-       (startsWith(github.event.pull_request.title, 'release: release ') ||
-        startsWith(github.event.pull_request.title, 'ci(release): release '))) ||
+       startsWith(github.event.pull_request.title, 'build: release ')) ||
       (github.event_name == 'workflow_dispatch' && inputs.mode == 'dry-run')
     runs-on: ubuntu-latest
     steps:
@@ -110,7 +108,7 @@ jobs:
         run: go run "${{ env.PR_RELEASE_MODULE }}" dry-run --ci-output
 
   # Production release: runs when the release PR merges (commit subject
-  # starts with "release:" / "ci(release):"). pr-release does NOT tag or
+  # starts with "build: release "). pr-release does NOT tag or
   # publish — wire your own tag + publisher here (e.g. git-cliff
   # --bumped-version to derive the tag, then GoReleaser / npm publish using
   # RELEASE_BODY.md as the GitHub Release body).
@@ -120,8 +118,7 @@ jobs:
   #   if: |
   #     github.event_name == 'push' &&
   #     github.ref == 'refs/heads/main' &&
-  #     (startsWith(github.event.head_commit.message, 'release:') ||
-  #      startsWith(github.event.head_commit.message, 'ci(release):'))
+  #     startsWith(github.event.head_commit.message, 'build: release ')
   #   runs-on: ubuntu-latest
   #   steps:
   #     - uses: actions/checkout@v4

skills/releasepr/references/release-notes.md

@@ -15,9 +15,9 @@ using `git-cliff` (config: `cliff.toml` in the repo). Use Conventional Commits:
 If no commit since the last tag warrants a bump, no release PR is produced.
 Force a release anyway with `pr-release pr-release --force`.
 
-Never hand-write a commit whose subject starts with `release:` or
-`ci(release):` on the default branch — that prefix triggers the production
-release job (see `release-workflow.md`).
+Reserve commits whose subject starts with `build: release ` on the default
+branch for generated release PRs — that prefix triggers the production release
+job (see `release-workflow.md`).
 
 ## Custom release notes with `add-note`
 

skills/releasepr/references/release-workflow.md

@@ -22,13 +22,13 @@
    runs `pr-release dry-run` to validate the release end-to-end without
    publishing.
 3. **Production release** — when the release PR merges, the merge commit (whose
-   subject starts with `release:` or `ci(release):`) triggers tagging and a
+   subject starts with `build: release `) triggers tagging and a
    GoReleaser publish.
 
 ## What triggers the release-PR job
 
 On push to the default branch, the job runs **unless** the head commit subject
-starts with `release:`, `ci(release):`, or `Merge pull request`, or the commit
+starts with `build: release ` or `Merge pull request`, or the commit
 author is `github-actions[bot]`. It also runs on manual dispatch with mode
 `release-pr`. This is why ordinary `feat:` / `fix:` commits produce a release PR
 but the release commit itself does not loop.
@@ -46,7 +46,7 @@ dispatch input).
 ## What triggers the dry-run job
 
 The dry-run job runs when a pull request whose title starts with
-`release: release ` or `ci(release): release ` is opened/synchronized/reopened
+`build: release ` is opened/synchronized/reopened
 against the default branch, or on manual dispatch with mode `dry-run` (passing
 `head_ref` and `pr_number`).
 
@@ -59,8 +59,8 @@ just from running `pr-release pr-release`.
 
 ## What triggers the production release
 
-A push to the default branch whose head commit subject starts with `release:`
-or `ci(release):` — i.e. the release PR being merged. The consumer's release
+A push to the default branch whose head commit subject starts with `build: release `
+— i.e. the release PR being merged. The consumer's release
 job (not pr-release) then:
 
 1. Derives the version with `git cliff --bumped-version` (fallback: parse it
@@ -71,8 +71,8 @@ job (not pr-release) then:
    `--release-header-tmpl=.goreleaser.release-header.md.tmpl`,
    `--release-footer-tmpl=.goreleaser.release-footer.md.tmpl`.
 
-Do not hand-author `release:` commits on the default branch — that is the
-trigger that publishes a production release.
+Reserve `build: release ` commits on the default branch for generated release
+PRs — that prefix publishes a production release.
 
 ## Explicit beta, stable, and legacy releases
 
@@ -112,7 +112,7 @@ these values with `git describe` in the consuming workflow.
 ## Branch and PR naming
 
 - Release branch: `release/vMAJOR.MINOR.PATCH`.
-- Release PR title: `release: release vX.Y.Z` (or `ci(release): release vX.Y.Z`).
+- Release PR title: `build: release vX.Y.Z`.
 - These exact prefixes are matched by the CI `if:` conditions; renaming them
   breaks the dry-run and production-release triggers.
 
@@ -131,8 +131,8 @@ these values with `git describe` in the consuming workflow.
 Check in this order:
 1. Were the commits conventional (`feat:`/`fix:`/etc.)? Non-conventional
    commits yield no version bump → no release PR. (`release-notes.md`)
-2. Was the push commit one of the skipped kinds (bot / `release:` /
-   `ci(release):` / `Merge pull request`)? Then the release-PR job did not run
+2. Was the push commit one of the skipped kinds (bot / `build: release ` /
+   `Merge pull request`)? Then the release-PR job did not run
    by design.
 3. Did owner/repo and token resolve? (`configuration.md`,
    `troubleshooting.md`)

skills/releasepr/references/troubleshooting.md

@@ -15,9 +15,9 @@ Match the exact error or symptom to a row before proposing a fix.
 | `release_artifacts[i].add must include at least one path or glob` / `path must be repository-relative` / `path cannot contain traversal` | Missing/invalid `add` entry. | Provide ≥ 1 repo-relative path/glob, no absolute paths, no `..`. |
 | `release_artifacts[i].timeout_seconds must be between 1 and 3600` | Out-of-range timeout. | Use 1–3600, or omit (`0` = unset). |
 | `config validation failed: invalid log_level` / `invalid log_format` | Value outside the allowed set. | `log_level` ∈ debug/info/warn/error; `log_format` ∈ json/console. |
-| Dry-run CI job never runs on the release PR | PR title prefix not matched. | Keep the title `release: release vX.Y.Z` or `ci(release): release vX.Y.Z`; do not rename the release branch pattern. See `release-workflow.md`. |
-| Production release never fires after merge | Merge commit subject not `release:`/`ci(release):`, or pushed to a non-default branch. | Merge the release PR so the release commit lands on the default branch with the expected subject prefix. |
-| Release-PR job did not run on a normal push | Head commit was a skipped kind (bot, `release:`, `ci(release):`, `Merge pull request`). | Expected by design. Push a regular conventional commit, or dispatch the workflow with mode `release-pr`. |
+| Dry-run CI job never runs on the release PR | PR title prefix not matched. | Keep the title `build: release vX.Y.Z`; do not rename the release branch pattern. See `release-workflow.md`. |
+| Production release never fires after merge | Merge commit subject does not start with `build: release `, or it was pushed to a non-default branch. | Merge the generated release PR so its title becomes the default-branch commit subject. |
+| Release-PR job did not run on a normal push | Head commit was a skipped kind (bot, `build: release `, `Merge pull request`). | Expected by design. Push a regular conventional commit, or dispatch the workflow with mode `release-pr`. |
 | Follow-up workflows not dispatched from the release-PR job | Default `GITHUB_TOKEN` cannot trigger other workflows. | Use a dedicated `RELEASE_TOKEN` PAT/app token for that job. |
 | Wrong / unexpectedly low version, or always the initial version | Shallow checkout — no history/tags for `git-cliff`. | `actions/checkout@v4` with `fetch-depth: 0` and `fetch-tags: true`. See `setup.md`. |
 | First-ever release picks `v0.0.x` off `v0.0.0` instead of intended baseline | Repo has no tags and `INITIAL_VERSION` is unset. | Set `INITIAL_VERSION` (e.g. `v0.0.1`) in the workflow env. See `configuration.md`. |