Update to transformers 5.0

[mergennachin]

No description provided.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16875

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 12 New Failures, 7 Cancelled Jobs, 1 Unrelated Failure

As of commit c6acd95 with merge base ecc7dd0 ():

NEW FAILURES - The following jobs have failed:

• pull / test-eval_llama-wikitext-linux / linux-job (gh)
  AttributeError: module transformers has no attribute AutoModelForVision2Seq
• pull / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  AttributeError: module transformers has no attribute AutoModelForVision2Seq
• pull / unittest / linux / linux-job (gh)
  extension/llm/tokenizers/test/test_hf_tokenizer.py::TestHfTokenizer::test_phi_4_mini
• pull / unittest / macos / macos-job (gh)
  extension/llm/tokenizers/test/test_hf_tokenizer.py::TestHfTokenizer::test_phi_4_mini
• pull / unittest-editable / linux / linux-job (gh)
  extension/llm/tokenizers/test/test_hf_tokenizer.py::TestHfTokenizer::test_phi_4_mini
• pull / unittest-editable / macos / macos-job (gh)
  extension/llm/tokenizers/test/test_hf_tokenizer.py::TestHfTokenizer::test_phi_4_mini
• Test CUDA Builds / test-model-cuda-e2e (mistralai, Voxtral-Mini-3B-2507, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t f2d5cbd40cef21654ca8b2ca35685fea36f17bc4cd6148fc16b114f2156e69e3 /exec failed with exit code 1
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-3B-2507, non-quantized) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• trunk / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  AttributeError: module transformers has no attribute AutoModelForVision2Seq
• trunk / test-mcu-cortex-m-backend / linux-job (gh)
  RuntimeError: Command docker exec -t 13344aa94c2f411bccd1bf69aa98e6a3f97d7b138edfcc3f191601f08325a38f /exec failed with exit code 1
• trunk / unittest-release / linux / linux-job (gh)
  extension/llm/tokenizers/test/test_hf_tokenizer.py::TestHfTokenizer::test_phi_4_mini
• trunk / unittest-release / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_linear_model

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• Lint / link-check / lint-file-size / linux-job (gh)
  ##[error]The operation was canceled.
• pull / test-lora-linux / linux-job (gh)
  ##[error]The operation was canceled.
• pull / test-multimodal-linux (gemma3-4b) / linux-job (gh)
  ##[error]The operation was canceled.
• pull / test-static-llama-qnn-linux (stories_110m) / linux-job (gh)
  ##[error]The operation was canceled.
• pull / test-static-llama-qnn-linux (stories_260k_bc) / linux-job (gh)
  ##[error]The operation was canceled.
• trunk / test-demo-backend-delegation (buck2) / linux-job (gh)
  ##[error]The operation was canceled.
• trunk / test-demo-backend-delegation (cmake) / linux-job (gh)
  ##[error]The operation was canceled.

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• trunk / test-qnn-model (fp32, mv2) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[Copilot]

Pull request overview

This PR updates the transformers library dependency from version 5.0.0rc1 (release candidate) and 4.56.1 to >= 5.0.0 (stable release) across two requirements files. This change moves from pinned pre-release and older stable versions to a minimum version constraint allowing any transformers version 5.0.0 or later.

Changes:

• Updated requirements-examples.txt from transformers == 5.0.0rc1 to transformers >= 5.0.0
• Updated .ci/docker/requirements-ci.txt from transformers==4.56.1 to transformers>=5.0.0

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
requirements-examples.txt	Updates transformers from RC version to stable >= 5.0.0 for example dependencies
.ci/docker/requirements-ci.txt	Updates transformers from 4.56.1 to >= 5.0.0 for CI environment dependencies

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The update to transformers >= 5.0.0 conflicts with documentation that explicitly states support for transformers v4.56.1. The file examples/models/phi-3-mini/README.md (line 7) states "Currently, we support transformers v4.56.1" and provides installation instructions for that specific version. This documentation needs to be updated to reflect the new version requirement, or the compatibility should be verified and documented.

Suggested change

	transformers >= 5.0.0
	transformers == 4.56.1

[Copilot]

The update to transformers >= 5.0.0 appears incomplete. The file examples/arm/image_classification_example/requirements.txt still pins to transformers[torch] == 4.56.1. This version mismatch could cause inconsistencies between different examples. Consider updating examples/arm/image_classification_example/requirements.txt to align with this version requirement, or verify that the ARM example is compatible with transformers 5.0.0.

Suggested change

	transformers >= 5.0.0
	transformers[torch] == 4.56.1

[Copilot]

The transformers dependency in requirements-ci.txt is now specified as >=5.0.0, so CI will automatically install whatever future version of this third‑party package is published. If the transformers package or its distribution channel is ever compromised, a malicious release could be pulled into CI and execute arbitrary code with access to secrets or the ability to modify build artifacts. To reduce supply-chain risk, pin this dependency to a specific immutable version (or hash) and update it intentionally rather than via an open version range.