chore(deps-dev): update transformers requirement from >=4.40 to >=5.5.3

[dependabot]

Updates the requirements on transformers to permit the latest version.

Release notes

Sourced from transformers's releases.

Patch release: v5.5.3

Small patch release to fix device_map support for Gemma4! It contains the following commit:

• [gemma4] Fix device map auto (#45347) by @​Cyrilvallez

Commits

• c6c8503 Release: v5.5.3
• dccd162 [gemma4] Fix device map auto (#45347)
• 52d24b0 Release: 5.5.2
• 5df3452 [gemma4] Remove all shared weights, and silently skip them during loading (#4...
• 2cf8ff0 Fix conversion mappings for vlms (#45340)
• 286e789 [gemma4] Dissociate kv states sharing from the Cache (#45312)
• 23c562c Add MoE to Gemma4 TP plan (#45219)
• a1b90c4 v5.5.1
• 4f8e2bb Fix export for gemma4 and add Integration tests (#45285)
• d30a963 Fix vllm cis (#45139)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[greptile-apps]

Greptile Summary

This PR bumps the transformers dev/train dependency from >=4.40 to >=5.5.3, a major version upgrade. The only consumer of transformers in the codebase is src/hippofloop/training/trainer.py, which imports TrainingArguments — an API that remains stable in v5.

• The unsloth[colab-new]>=2024.8 lower bound predates transformers v5 support in unsloth (added ~December 2024). Pip could theoretically satisfy both constraints with an incompatible combination (old unsloth + new transformers). Bumping the unsloth lower bound to a version confirmed to support transformers v5 would make this safer.

Confidence Score: 4/5

Safe to merge after addressing the unsloth version lower bound to ensure compatibility with transformers v5.

The only transformers API used in the codebase (TrainingArguments) is stable across the v4→v5 boundary, so no code changes are needed. However, the unsloth lower bound (>=2024.8) predates transformers v5 support and could allow a pip resolver to produce an incompatible environment, warranting a small bump before merging.

pyproject.toml — unsloth version constraint should be tightened alongside the transformers bump.

Important Files Changed

Filename	Overview
pyproject.toml	Single-line change bumping transformers from >=4.40 to >=5.5.3 (major version); unsloth lower bound may not guarantee transformers v5 compatibility.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[pip install hippofloop train] --> B{Resolve dependencies}
    B --> C[transformers >= 5.5.3\nresolves to latest v5]
    B --> D[unsloth >= 2024.8\ncould resolve to Aug 2024 build]
    D -->|Old unsloth 2024.8| E[No transformers v5 support\nRuntime incompatibility]
    D -->|New unsloth 2024.12+| F[transformers v5 supported\nCompatible environment]
    C --> E
    C --> F

Loading

_{Reviews (1): Last reviewed commit: "chore(deps-dev): update transformers req..." | Re-trigger Greptile}

[greptile-apps]

Unsloth lower bound may not cover transformers v5 support

unsloth[colab-new]>=2024.8 allows installing unsloth versions from August 2024, but transformers v5 support was only added to unsloth in ~December 2024. A resolver that picks an older compliant unsloth (e.g. 2024.8.x) alongside transformers==5.5.3 will produce an incompatible environment at runtime. Consider tightening the unsloth lower bound to a release known to support transformers v5 (e.g. >=2024.12).