[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
mcp-remote	0.15.1 → 0.15.2

---

Release Notes

punkpeye/mcp-remote (mcp-remote)

v0.15.2

Compare Source

Bug Fixes

• open the browser for the client registered after a stale one is cleared (#​383) (373f732)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.

[apify-factory]

Looks good, nothing blocking.

🏭 Factory review — ℹ️ not auto-approved

This change was reviewed but cannot be auto-approved: a human review is active (l2ysho: APPROVED).

check	result
Static gates	❌ 12/16 — author-is-human, author-allowed, file-extensions, deny-globs
Review findings	✅ none
Reviewer escalation	❌ Supply-chain change: bumps the pinned third-party mcp-remote package (which handles OAuth client registration), whose new code cannot be verified from the diff alone.
Juror 1 — claude-sonnet-5-5, adversarial	⏭️ skipped — a gate failed

Why it was not auto-approved

Failed gates:

• author-is-human: author renovate[bot] is not a human user
• author-allowed: renovate[bot]: not a member of apify/product-engineering
• file-extensions: disallowed extension: templates/ts-mcp-proxy/package.json
• deny-globs: templates/ts-mcp-proxy/package.json matches **/package.json

The comments above are the review itself; this section only explains the approval decision. Push a change and request @apify-factory again to re-run it, or ask a human to review.

_{Reviewed 3cd8826b2 · workflow run}