ci(github-action): update action misospace/pr-reviewer-action (v1.2.3 → v1.2.4)

[its-miso]

This PR contains the following updates:

Package	Type	Update	Change
misospace/pr-reviewer-action	action	patch	v1.2.3 → v1.2.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

misospace/pr-reviewer-action (misospace/pr-reviewer-action)

v1.2.4

Compare Source

Feature-bearing 1.2.x release (1.3.0 remains reserved for the native tool-calling work tracked in #​197). Backward-compatible: no new inputs — the thread-lifecycle features are gated by the existing inline_findings input and engage automatically on incremental reviews.

Features

• Inline finding threads are resolved when the finding is fixed (#​208): every inline comment now carries a hidden content fingerprint of its finding. When a later incremental review's carry-forward concludes a carried finding is resolved (the model answers it resolved — the same fail-closed rule that drives the verdict), the matching open review thread is resolved via the GraphQL resolveReviewThread mutation. Authors see live thread state instead of stale open conversations. Threads are matched by marker, never by author (#​190); all API failures (e.g. read-only fork tokens) warn and never fail the publish.
• Still-open findings reply on their existing thread instead of duplicating (#​209): a carried finding that survives the review (still_open / not_verifiable_from_delta / unanswered) gets a short follow-up reply on its existing thread, stamped with the head SHA so re-runs never stack duplicates, and capped by inline_findings_max. The comment builder suppresses fresh anchored comments for findings that already have a live thread — one conversation per finding across N pushes. Findings the model marked resolved no longer produce fresh anchored comments either. A still-open finding whose thread disappeared falls back to a fresh comment as before.

Fixes

• Carry-forward now engages in publish_mode: comment (#​212): the comment-mode publish step never passed FINDINGS into the metadata marker, so open_findings was always empty and the fail-closed carry-forward (#​193) silently never ran in that mode. Incremental scope and skip-on-unchanged were unaffected; the findings safety net now works in all three publish modes.

Internal

• CI dogfooding pins bumped and smart-model vars wired explicitly (#​199, #​200).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[its-miso]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: review@https://litellm.jory.dev/v1 (openai)

Recommendation

Approved. This is a routine dependency update for the misospace/pr-reviewer-action GitHub Action, moving from v1.2.3 to v1.2.4. The update is performed by Renovate Bot and includes critical features for the action's thread-lifecycle management.

Change-by-Change Findings

.github/workflows/ai-pr-review.yaml

• Dependency Update: Updated misospace/pr-reviewer-action from SHA e891235... (v1.2.2/v1.2.3) to SHA d1a7753... (v1.2.4).
• Configuration Updates:
  • Updated ai_primary_retries from 8 to 3.
  • Added ai_response_format: json_object.
  • Added review_routing_mode: auto.
  • Added ai_smart_* configuration parameters (URL, format, model, API key).
  • Updated tool_mode from plan_execute_once to plan_execute_loop and added tool_max_rounds: "2".
  • Added on_model_failure: notice.
  • Added inline_findings: "true".
  • Added verdict_policy: findings_severity_gated.
• Security/Best Practice: The update uses a specific commit SHA for the action, which is a good security practice to prevent supply chain attacks via tag shifting.

README.md and action.yml

• Documentation: Updated README.md to include documentation for the new thread lifecycle features (resolving threads when findings are fixed and replying to still-open findings).
• Outputs: Updated action.yml to expose the FINDINGS output, which is required for the new thread-management logic in the workflow.

Standards Compliance

• Dependency Management: Follows the repository's pattern of pinning actions to specific SHAs for security.
• Documentation: Updates documentation in tandem with functional changes.

Linked Issue Fit

• The release notes indicate this update addresses several issues related to finding thread lifecycles (PR 208, PR 209) and carry-forward logic (PR 212), which are correctly reflected in the configuration changes (e.g., inline_findings: "true").

Unknowns or Needs Verification

• None. The changes are consistent with the provided release notes for v1.2.4.