Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Guard MiniMax OAuth fetches in bundled plugin runtime [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Problem

The MiniMax OAuth runtime raw fetches have been migrated to guarded fetches on current main, but the no-raw-channel-fetch boundary checker still contains the two old MiniMax OAuth allowlist entries:

  • bundledPluginCallsite("minimax", "oauth.ts", 82)
  • bundledPluginCallsite("minimax", "oauth.ts", 123)

Those stale exemptions keep the checker baseline looser than the current code requires.

Proposed fix

Remove the obsolete MiniMax OAuth raw-fetch allowlist entries and keep the remaining MiniMax TTS legacy exemption unchanged.

Validation

  • node scripts/check-no-raw-channel-fetch.mjs
  • git diff --check

Fix PR: #88086

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Guard MiniMax OAuth fetches in bundled plugin runtime [1 pull requests]