Skip to content

merge queue: checking release/v3.8.49 (7123236), #7128, #7136, #7042, #7093 and #7098 together - #7457

Closed
mergify[bot] wants to merge 19 commits into
release/v3.8.49from
mergify/merge-queue/b3b98aab16
Closed

mergify[bot] wants to merge 19 commits into
release/v3.8.49from
mergify/merge-queue/b3b98aab16

Conversation

@mergify

@mergify mergify Bot commented Jul 16, 2026 •

Copy link
Copy Markdown

✨ Pull request #7042 ahead in the queue was removed (reason: pull request dequeued). The pull request #7098 has been requeued. ✨

Branch release/v3.8.49 (7123236), #7128, #7136, #7042, #7093 and #7098 are queued together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #7098.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule release for merge:

  • #check-pending=0
  • check-success=Merge integrity (changelog + generated skills)
  • #check-success>=1
  • any of:
    • #check-failure=0
    • all of:
      • #check-failure=1
      • check-failure=dast-smoke

Required conditions to stay in the queue:

---
checking_base_sha: ba6851586119b3a968fb52aceceeaa770c3f2f52
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 7098
    scopes: []
scopes: []
...

alltomatos and others added 19 commits July 13, 2026 09:47
…ort from 9router#1321)

The reasoning_content injector already handles DeepSeek/Kimi/K2/MiniMax thinking-mode upstreams, echoing a placeholder reasoning_content on assistant turns that lack one. Its THINKING_MODEL_PATTERNS list omitted the xiaomi-tokenplan mimo family, so requests through xiaomi-tokenplan/mimo-v2.5-pro still hit upstream's 400 'reasoning_content in the thinking mode must be passed back to the API', making the model unusable in multi-turn conversations (e.g. Codex CLI). Add a /\bmimo\b/i pattern so mimo models get the same treatment.

Reported-by: z.wl (@xxue-z) (decolua/9router#1321)
@mergify mergify Bot closed this Jul 16, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/b3b98aab16 branch July 16, 2026 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants