feat: upgrade transformers to v4.56.1

[NanoCode012]

Description

Is needed for:

• Feat: add seedoss #3104
• Feat: add hunyuan v1 #3016

Motivation and Context

How has this been tested?

Screenshots (if appropriate)

Types of changes

Social Handles (Optional)

Summary by CodeRabbit

• Chores
  • Updated Transformers dependency from 4.55.4 to 4.56.0.
  • No other dependencies were modified.
  • No new features or UI changes introduced.
  • Typical functionality and workflows should remain consistent.
  • No configuration changes or user action required.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

The transformers dependency in requirements.txt is updated from version 4.55.4 to 4.56.0. No other files or dependencies are modified.

Changes

Cohort / File(s)	Summary of Changes
Dependency version bump requirements.txt	Update pin: transformers 4.55.4 → 4.56.0; no other lines changed

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• upgrade transformers==4.55.0 #3018 — Also bumps transformers in requirements.txt (to 4.55.0).
• use updated patch release transformers 4.55.2 #3066 — Updates the same transformers pin (to 4.55.2).
• upgrade transformers==4.55.1 and bitsandbytes==0.47.0 #3064 — Version bump of transformers in requirements.txt, same line modified.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/transformers-v456

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[winglian]

need this fix upstream to fix broken offline mode in transformers huggingface/transformers#40669

[NanoCode012]

@winglian , should we just monkeypatch it for now?