ci(github-action): update action misospace/pr-reviewer-action (v1.3.0 → v1.3.1)

[its-miso]

This PR contains the following updates:

Package	Type	Update	Change
misospace/pr-reviewer-action	action	patch	v1.3.0 → v1.3.1

---

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.3.1: — Routing fix: the primary model gets its full tool budget

Compare Source

v1.3.1 — Routing fix: the primary model gets its full tool budget

A bug-fix release for review_routing_mode: auto. The auto router was sending low-risk PRs (e.g. a renovate dependency bump) to a shallow lane that capped the loop's tool budget — starving exactly the multi-hop chains (read the changed config → search → fetch the compatibility matrix → cite) that the v1.3.0 native loop was built to run. All changes are backward-compatible via deprecated aliases.

Fixes

• The primary route gets the full configured tool budget. Removed the route-based shallow cap — the loop self-limits, so the cap only ever starved chain-needing PRs. The route now selects the model, not the budget (#​278).
• The smart tier only escalates when explicitly configured. ai_smart_* no longer falls back to ai_fallback_*: with no ai_smart_model set, a review stays on the primary model instead of silently escalating to the fallback. The fallback model is for availability, not quality escalation (#​278).

Rename (backward-compatible)

• The fast route is now primary — a capable primary model shouldn't be rationed like a "fast/dumb" lane. Inputs ai_fast_* → ai_primary_*, with ai_fast_* retained as deprecated aliases, so no workflow changes are needed to upgrade. The review_route output and engine annotation now read primary; the per-route artifact is ai-output.primary.json (#​278).

---

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: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_low_confidence)

Review Summary

PR PR 423: Patch version update to misospace/pr-reviewer-action from v1.3.0 → v1.3.1

Recommendation: APPROVE

---

Change Overview

This PR updates a single pinned SHA reference in the AI PR review GitHub Actions workflow, bumping the misospace/pr-reviewer-action from v1.3.0 to v1.3.1.

---

v1.3.1 Release Analysis

The v1.3.1 release is titled "Routing fix: the primary model gets its full tool budget" and contains:

1. Bug Fix - Full tool budget for primary route: Removed a route-based shallow cap that was starving multi-hop tool chains on low-risk PRs. The route now selects the model, not the budget.

2. Bug Fix - Smart tier escalation behavior: ai_smart_* inputs no longer silently fall back to ai_fallback_*. Without explicit ai_smart_model configuration, reviews stay on the primary model.

3. Rename (backward-compatible): The fast route is renamed to primary; ai_fast_* inputs remain as deprecated aliases.

---

Compatibility Verification

The workflow file (.github/workflows/ai-pr-review.yaml) already uses the new ai_primary_* input naming convention (e.g., ai_primary_retries, ai_primary_retry_delay_sec), so this workflow is fully compatible with v1.3.1. The deprecated ai_fast_* aliases are present in the action's README but are not used here.

The workflow's configuration aligns with v1.3.1's supported parameters:

• review_routing_mode: auto — supported
• tool_mode: native_loop — supported (introduced in v1.3.0)
• ai_primary_* inputs — supported (new naming)

---

CI Validation

Both CI checks completed successfully:

• Docker Build: ✅ success
• Validate: ✅ success

---

Standards Compliance

• ✅ GitHub Actions follow pinning convention with full SHA references
• ✅ No secrets committed
• ✅ No changes to Prisma schema
• ✅ No changes to API routes or business logic

---

Linked Issue Fit

No linked issues. This is a straightforward patch version dependency update.

---

Unknowns / Needs Verification

None. The version bump is well-documented in release notes, CI passes, and the workflow is already using the action's new parameter naming convention.

---

Findings

No blocking, major, minor, or informational issues identified.