fix(release): merge develop into main

[bedatty]

GitHub Actions Shared Workflows

---

Description

Type of Change

• feat: New workflow or new input/output/step in an existing workflow
• fix: Bug fix in a workflow (incorrect behavior, broken step, wrong condition)
• perf: Performance improvement (e.g. caching, parallelism, reduced steps)
• refactor: Internal restructuring with no behavior change
• docs: Documentation only (README, docs/, inline comments)
• ci: Changes to self-CI (workflows under .github/workflows/ that run on this repo)
• chore: Dependency bumps, config updates, maintenance
• test: Adding or updating tests
• BREAKING CHANGE: Callers must update their configuration after this PR

Breaking Changes

None.

Testing

• YAML syntax validated locally
• Triggered a real workflow run on a caller repository using @develop or the beta tag
• Verified all existing inputs still work with default values
• Confirmed no secrets or tokens are printed in logs
• Checked that unrelated workflows are not affected

Caller repo / workflow run:

Related Issues

Closes #

Summary by CodeRabbit

• New Features

  • Release workflow tolerates semantic-release failures and can fall back to creating a backmerge pull request; added a reusable backmerge-PR step.

• Documentation

  • Updated release docs to describe backmerge fallback and added docs for the backmerge step; updated PR-validation docs to focus on checkbox-based checks.

• Chores

  • Pinned shared workflow references to v1.20.1 and removed the PR description minimum-length input, simplifying validation.

[lerian-studio]

🛡️ CodeQL Analysis Results

Languages analyzed: actions

✅ No security issues found.

---

_{🔍 View full scan logs | 🛡️ Security tab}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/release-workflow.md (1)

82-85: ⚠️ Potential issue | 🟡 Minor

Inputs table is out of sync with the workflow.

The workflow defines filter_paths, shared_paths, and path_level inputs for monorepo support, but these are missing from the documentation.

📝 Proposed fix to add missing inputs

 | Input | Type | Default | Description |
 |-------|------|---------|-------------|
 | `semantic_version` | string | `23.0.8` | Semantic release version to use |
 | `runner_type` | string | `firmino-lxc-runners` | GitHub runner type |
+| `filter_paths` | string | `''` | Newline-separated list of path prefixes to filter. If not provided, treats as single app repo. |
+| `shared_paths` | string | `''` | Newline-separated path patterns that trigger a build for ALL components when matched. |
+| `path_level` | string | `'2'` | Limits the path to the first N segments (e.g., 2 → "apps/agent") |

As per coding guidelines: "Flag if inputs table is out of sync with the corresponding workflow changes in this PR."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/release-workflow.md` around lines 82 - 85, The inputs table in
release-workflow.md is missing the monorepo-related workflow inputs; update the
table to include `filter_paths`, `shared_paths`, and `path_level` with their
correct types (likely `string` or `string[]` as used in the workflow), sensible
defaults, and clear descriptions matching the workflow behavior (e.g.,
`filter_paths` — paths to watch for changes, `shared_paths` — paths shared
across packages, `path_level` — depth level for package path resolution); ensure
the names exactly match the workflow input keys so docs stay in sync with the
workflow (reference inputs `filter_paths`, `shared_paths`, `path_level` and
adjust types/defaults to match the workflow implementation).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/pr-validation.yml:
- Line 122: Replace the mutable feature-branch ref for the reusable workflow
pr-blocking-collect with a stable release tag: change the uses entry
"LerianStudio/github-actions-shared-workflows/src/validate/pr-blocking-collect@fix/pin-refs-v1.20.0"
to reference the repository's released tag (for example "@v1.20.0" or the
appropriate published release) so the workflow uses a permanent, non-mutable
ref.

---

Outside diff comments:
In `@docs/release-workflow.md`:
- Around line 82-85: The inputs table in release-workflow.md is missing the
monorepo-related workflow inputs; update the table to include `filter_paths`,
`shared_paths`, and `path_level` with their correct types (likely `string` or
`string[]` as used in the workflow), sensible defaults, and clear descriptions
matching the workflow behavior (e.g., `filter_paths` — paths to watch for
changes, `shared_paths` — paths shared across packages, `path_level` — depth
level for package path resolution); ensure the names exactly match the workflow
input keys so docs stay in sync with the workflow (reference inputs
`filter_paths`, `shared_paths`, `path_level` and adjust types/defaults to match
the workflow implementation).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 6ece92ad-142f-4cc6-88cb-9a8e5b87f9e7

📥 Commits

Reviewing files that changed from the base of the PR and between e87492a and 9b488d4.

📒 Files selected for processing (5)

• .github/workflows/pr-validation.yml
• .github/workflows/release.yml
• docs/release-workflow.md
• src/validate/pr-blocking-collect/README.md
• src/validate/pr-blocking-collect/action.yml

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/config/backmerge-pr/action.yml`:
- Around line 50-56: The PR_BODY multi-line string is indented in the script so
every line gets leading spaces; replace the inline quoted assignment with a
heredoc to preserve intended formatting — e.g. set PR_BODY using PR_BODY=$(cat
<<'EOF' ... EOF) (or <<-'EOF' if you need to strip leading tabs) and paste the
unindented markdown between the EOF markers; update the assignment that
currently defines PR_BODY in action.yml to use this heredoc form so the PR
description has no unwanted leading whitespace.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4bb17dc6-4382-4f61-93ee-f326e51150ab

📥 Commits

Reviewing files that changed from the base of the PR and between 9b488d4 and c8b2867.

📒 Files selected for processing (4)

• .github/workflows/pr-validation.yml
• .github/workflows/release.yml
• src/config/backmerge-pr/README.md
• src/config/backmerge-pr/action.yml

All comments addressed.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/config/backmerge-pr/action.yml`:
- Around line 19-25: The output description for pr-url is incorrect relative to
the implementation: update the outputs block to reflect actual behavior (or
change the behavior). Specifically, either modify the description of
outputs.pr-url (and optionally outputs.pr-number) to state that pr_url is
populated even when an existing PR is found (it comes from
steps.create-pr.outputs.pr_url), or change the logic in the create-pr step to
leave pr_url empty for existing PRs; reference the outputs keys
"pr-url"/"pr-number" and the step "steps.create-pr.outputs.pr_url" to locate
where to update the description or behavior.
- Around line 50-59: The YAML parse error comes from the unindented heredoc
assigned to PR_BODY inside the run: | block; update the PR_BODY heredoc so all
its lines (the "## Description" line through the closing EOF) are indented to
the same level as the first content line inside the block scalar, ensuring the
closing EOF matches that indentation, or alternatively replace the heredoc with
an indented read-style heredoc variant; make this change around the PR_BODY
assignment that references VERSION, SOURCE_BRANCH and TARGET_BRANCH so the
pipeline no longer fails YAML validation.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 709270f7-ce2a-422b-aedf-eb0a5d39c3cf

📥 Commits

Reviewing files that changed from the base of the PR and between c8b2867 and b18a15d.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• src/config/backmerge-pr/action.yml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Output description contradicts implementation.

Line 21 states pr-url is "empty if PR already existed" but the implementation at lines 43-46 sets pr_url for existing PRs. Either update the description or the behavior.

Suggested fix

 outputs:
   pr-url:
-    description: URL of the created PR (empty if PR already existed or was not needed)
+    description: URL of the created or existing backmerge PR
     value: ${{ steps.create-pr.outputs.pr_url }}
   pr-number:
     description: Number of the created or existing PR

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/backmerge-pr/action.yml` around lines 19 - 25, The output
description for pr-url is incorrect relative to the implementation: update the
outputs block to reflect actual behavior (or change the behavior). Specifically,
either modify the description of outputs.pr-url (and optionally
outputs.pr-number) to state that pr_url is populated even when an existing PR is
found (it comes from steps.create-pr.outputs.pr_url), or change the logic in the
create-pr step to leave pr_url empty for existing PRs; reference the outputs
keys "pr-url"/"pr-number" and the step "steps.create-pr.outputs.pr_url" to
locate where to update the description or behavior.

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

.github/workflows/pr-validation.yml (2)

135-135: ⚠️ Potential issue | 🟡 Minor

Fix yamllint spacing warning.

Pipeline reports: "too few spaces before comment: expected 2".

Proposed fix

-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/pr-validation.yml at line 135, Yamllint warns about too
few spaces before the inline comment on the uses line; update the line
containing "uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd #
v6" to ensure there are two spaces before the "#" (i.e., replace the single
space before the comment with two spaces); also scan for other inline comments
in the workflow file and apply the same two-space convention to satisfy
yamllint.

---

198-204: 🧹 Nitpick | 🔵 Trivial

Line-length warnings are non-blocking.

Lines 200 and 202 exceed 200 characters. Per repo configuration, line-length is a warning, not an error. These long lines are due to inline ternary expressions for status/failed_jobs. Refactoring is optional but would improve readability.

Optional: Extract status logic to a prior step

      - name: Compute notification status
        id: notify-status
        run: |
          if [[ "${{ needs.blocking-checks.outputs.source-branch-result }}" == "failure" ]] || \
             [[ "${{ needs.blocking-checks.outputs.title-result }}" == "failure" ]] || \
             [[ "${{ needs.blocking-checks.outputs.description-result }}" == "failure" ]]; then
            echo "status=failure" >> "$GITHUB_OUTPUT"
          else
            echo "status=success" >> "$GITHUB_OUTPUT"
          fi

Then reference ${{ steps.notify-status.outputs.status }} in the workflow call.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/pr-validation.yml around lines 198 - 204, The long inline
ternaries in the GitHub Actions call to
LerianStudio/github-actions-shared-workflows (the "uses: ... slack-notify.yml"
step) cause >200 char lines; extract the logic into prior steps (e.g., a step
with id notify-status to compute a single status output and optionally a step
like notify-failed-jobs to assemble the failed_jobs string) and then pass those
outputs into the workflow call via ${{
steps.notify-status.outputs.status }} and ${{
steps.notify-failed-jobs.outputs.failed_jobs }} (update the "status" and
"failed_jobs" inputs to reference those step outputs instead of the inline
ternaries).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/validate/pr-description/action.yml`:
- Line 8: The YAML linter warning is caused by missing spacing before the inline
comment on the uses line; update the line containing uses:
actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd (the
actions/github-script version comment) to include two spaces before the "#" so
there is one space between the value and the comment (e.g., add a single space
before the version comment) to satisfy yamllint's "too few spaces before
comment" rule.

---

Outside diff comments:
In @.github/workflows/pr-validation.yml:
- Line 135: Yamllint warns about too few spaces before the inline comment on the
uses line; update the line containing "uses:
actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6" to ensure there
are two spaces before the "#" (i.e., replace the single space before the comment
with two spaces); also scan for other inline comments in the workflow file and
apply the same two-space convention to satisfy yamllint.
- Around line 198-204: The long inline ternaries in the GitHub Actions call to
LerianStudio/github-actions-shared-workflows (the "uses: ... slack-notify.yml"
step) cause >200 char lines; extract the logic into prior steps (e.g., a step
with id notify-status to compute a single status output and optionally a step
like notify-failed-jobs to assemble the failed_jobs string) and then pass those
outputs into the workflow call via ${{
steps.notify-status.outputs.status }} and ${{
steps.notify-failed-jobs.outputs.failed_jobs }} (update the "status" and
"failed_jobs" inputs to reference those step outputs instead of the inline
ternaries).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro

Run ID: b2936243-d239-48d9-822b-00af89b3b384

📥 Commits

Reviewing files that changed from the base of the PR and between b18a15d and 67ff2cc.

📒 Files selected for processing (3)

• .github/workflows/pr-validation.yml
• src/validate/pr-description/README.md
• src/validate/pr-description/action.yml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix yamllint spacing warning.

Pipeline reports: "too few spaces before comment: expected 2". Add a space before the version comment.

Proposed fix

-      uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8
+      uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd  # v8

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8
	uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8

🧰 Tools

🪛 GitHub Actions: Self — PR Validation

[warning] 8-8: Yamllint warning: too few spaces before comment: expected 2 (comments)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/validate/pr-description/action.yml` at line 8, The YAML linter warning is
caused by missing spacing before the inline comment on the uses line; update the
line containing uses:
actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd (the
actions/github-script version comment) to include two spaces before the "#" so
there is one space between the value and the comment (e.g., add a single space
before the version comment) to satisfy yamllint's "too few spaces before
comment" rule.

[coderabbitai]

♻️ Duplicate comments (1)

src/validate/pr-description/action.yml (1)

8-8: ⚠️ Potential issue | 🟡 Minor

Fix yamllint spacing warning.

Pipeline reports too few spaces before comment: expected 2. Add one space before #.

Proposed fix

-      uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8
+      uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd  # v8

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/validate/pr-description/action.yml` at line 8, The YAML linter warning is
due to only one space before the inline comment on the actions usage line; edit
the line that references
actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd (the uses: entry)
and add one more space so there are two spaces before the "# v8" comment,
resolving the "too few spaces before comment" yamllint error.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@src/validate/pr-description/action.yml`:
- Line 8: The YAML linter warning is due to only one space before the inline
comment on the actions usage line; edit the line that references
actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd (the uses: entry)
and add one more space so there are two spaces before the "# v8" comment,
resolving the "too few spaces before comment" yamllint error.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7fcf288c-2593-4c70-918f-545277c8fe25

📥 Commits

Reviewing files that changed from the base of the PR and between 67ff2cc and 3aa1a20.

📒 Files selected for processing (1)

• src/validate/pr-description/action.yml