Skip to content

fix: drop transformers 5.3.0 override - #984

Merged
danieldk merged 1 commit into
mainfrom
fix-drop-transformers-override
Nov 10, 2026
Merged

danieldk merged 1 commit into
mainfrom
fix-drop-transformers-override

Conversation

@drbh

@drbh drbh commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

this pr drops the transformers 5.3.0 override from nix-builder/overlay.nix so the builder uses the nixpkgs version (5.17.0)

the override was added in #400 when nixpkgs had a broken 4.57.3. nixpkgs caught up in #425 and since then the override only downgraded transformers. after the nixpkgs bump in #831 it conflicts with tokenizers 0.23.2, since 5.3.0 requires tokenizers<=0.23.0. this breaks the mamba-ssm ci-test https://github.com/huggingface/kernels-community/actions/runs/42704254952/job/129457078351

Checking runtime dependencies for transformers-5.3.0-py3-none-any.whl
  - tokenizers<=0.23.0,>=0.22.0 not satisfied by version 0.23.2

pythonRelaxDeps is not enough here since transformers checks the same pin again on import. nixpkgs 5.17.0 allows tokenizers<0.24.0 and already depends on typer

built the mamba-ssm ci-test python env on x86_64-linux with this branch as kernel-builder, transformers 5.17.0 and the env both build

nixpkgs now ships transformers 5.17.0, which already depends on typer.
the 5.3.0 override pins tokenizers<=0.23.0, but nixpkgs has 0.23.2, so
any kernel with transformers in its check inputs (mamba-ssm ci-test)
failed the runtime deps check and the import check
@danieldk
danieldk merged commit 5ee64be into main Nov 10, 2026
49 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants