Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Dependencies] Bump transformers to v5

Open
#53 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
huggingface, python

Research direction

Read pyproject.toml around line 22 and the linked huggingface_hub and transformers migration guides first. Check whether MOVA is compatible with transformers v5 and huggingface_hub 1.0; done means the dependency versions are updated without unresolved compatibility blockers.

Written by the indexing model from the issue text.

Description

Hey there! Maintainer of huggingface_hub library here, the underlying interface used by Python libraries to interact with the Hugging Face Hub 👋

A few months ago we've released huggingface_hub 1.0 and are adding new features to it regularly. This version is incompatible with transformers v4.x. Since transformers v5 has been shipped early 2026, I think it'd be beneficial to bump transformers to v5 - and therefore huggingface_hub v1.0. Let me know if there are any blockers doing so!

https://github.com/OpenMOSS/MOVA/blob/0a9cd51ffeab60f6fa0c7d48fbde5de40955b77b/pyproject.toml#L22

Note: we have a guide on how to migrate huggingface_hub (https://huggingface.co/docs/huggingface_hub/concepts/migration) and another one for transformers https://github.com/huggingface/transformers/blob/main/MIGRATION_GUIDE_V5.md. Hopefully it shouldn't be a huge effort. Potentially Mova is already compatible with them without any changes.

Dominant language
Python
Stars
1.1k
Forks
95
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenMOSS/MOVA

All issues in OpenMOSS/MOVA

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.