Pin huggingface_hub<1.0

[GregoryComer]

Summary

Trying to fix failing HF CI jobs. Looks like our transformers version requires huggingface_hub<1.0, but we're installing the latest 1.0 version which just released today. Until we bump transformers, I'll just pin our install of huggingface_hub to below 1.0.

Note that we don't pin the transformers version the same way for pip install, so this should be a ci only issue (and hence ci only fix).

Here's an example job failure:

transformers 4.56.1 requires huggingface-hub<1.0,>=0.34.0, but you have huggingface-hub 1.0.0 which is incompatible.
...
/exec: line 13: huggingface-cli: command not found

(from https://github.com/pytorch/executorch/actions/runs/18851188516/job/53787937311)

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⏳ 3 Pending, 3 Unrelated Failures

As of commit e774959 with merge base cd6f2e2 ():

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

• periodic / test-models-linux (cmake, mv3, portable, linux.2xlarge, 90) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest / linux / linux-job (gh) (trunk failure)
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)

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.

[GregoryComer]

Note that unit test ci failures are preexisting (getting to this next). Model test failure is a flake and I can't rerun until the whole pull job finishes. I'd like to land this one the relevant ci jobs pass to unbreak ci.

[GregoryComer]

@pytorchbot cherry-pick --onto release/1.0 -c critical

[pytorchbot]

Cherry picking #15399

Command git -C /home/runner/work/executorch/executorch cherry-pick -x -X theirs 57f0dfd9046351ad56c4caf5d1f1b42af6ee2573 returned non-zero exit code 1

CONFLICT (modify/delete): .github/workflows/cuda.yml deleted in HEAD and modified in 57f0dfd904 (Pin huggingface_hub<1.0 (#15399)).  Version 57f0dfd904 (Pin huggingface_hub<1.0 (#15399)) of .github/workflows/cuda.yml left in tree.
CONFLICT (modify/delete): .github/workflows/metal.yml deleted in HEAD and modified in 57f0dfd904 (Pin huggingface_hub<1.0 (#15399)).  Version 57f0dfd904 (Pin huggingface_hub<1.0 (#15399)) of .github/workflows/metal.yml left in tree.
Auto-merging .github/workflows/pull.yml
Auto-merging .github/workflows/trunk.yml
error: could not apply 57f0dfd904... Pin huggingface_hub<1.0 (#15399)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

Details for Dev Infra team

Raised by workflow job