[qgallouedec]

Version checks now compare against plain release versions: Version("5.18.0"), not Version("5.18.0.dev0"). A dev build of a version counts as the previous release.

• 0.19.2.dev0 becomes 0.20.0: 0.19.2 was never released, and Resolve #2944: ensure_weight_tying respects config + improved tests peft#3171 first shipped in 0.20.0.
• The 5.23.0.dev0 xfails in test_chat_template_utils.py are left as is, Handle a missing content key in the DeepSeek training chat templates #8228 removes them.

Side effect on the dev-deps CI (peft main is 0.21.3.dev0): the LoRA MoE warning fires there, and test_train_moe_with_peft_config_trains_all_mlp_layers is skipped, until peft 0.21.3 is released.

---

Note

Low Risk
Test and version-guard tuning only; no training logic changes, though dev-deps CI may see different skips/warnings until matching releases ship.

Overview
Version gates across trainers, chat_template_utils, and tests now compare against released version numbers (e.g. 5.18.0, 5.13.0, 0.20.0, 0.21.3) instead of *.dev0 prerelease strings.

Behavioral intent: a dev install like 5.18.0.dev0 is treated as below 5.18.0, so feature detection and skip/xfail conditions align with shipped releases rather than treating nightly main as already past the gate.

Notable threshold updates include PEFT ensure_weight_tying workarounds (0.19.0–< 0.20.0, with comments noting the fix landed in 0.20.0), MoE LoRA dense/shared-layer warnings (peft < 0.21.3), transformers response-template support (>= 5.13.0), VLM assistant-only loss (>= 5.18.0), and GRPO tool parsing without jmespath (>= 5.13.0).

^{Reviewed by Cursor Bugbot for commit 1da3185. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	❌ Failed 2026-11-11T20:41:26.676078Z We couldn’t complete this review. Comment @codex review to try again.	1da3185	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.