Skip to content

Remove unused image dependency (all core2 versions yanked)#115

Open
setoelkahfi wants to merge 1 commit into
openai:mainfrom
setoelkahfi:fix/remove-unused-image-dependency
Open

Remove unused image dependency (all core2 versions yanked)#115
setoelkahfi wants to merge 1 commit into
openai:mainfrom
setoelkahfi:fix/remove-unused-image-dependency

Conversation

@setoelkahfi
Copy link
Copy Markdown

@setoelkahfi setoelkahfi commented Apr 26, 2026

image = "0.25.6" is listed in [dependencies], but I could not find it used anywhere in src/. No use image, no extern crate image.

That would be harmless if the crate still resolved cleanly. It does not.

image enables AVIF support by default, which pulls in ravif -> rav1e -> bitstream-io -> core2. Every published version of core2 was yanked on April 14, 2026, so a fresh cargo build of openai-harmony now fails because Cargo cannot resolve that chain.

This PR removes the unused dependency and gets fresh downstream installs building again. As a side effect, Cargo.lock drops about 15 crates.

How I checked

# Confirm image is not referenced from src/
grep -r "use image\|extern crate image" src/
# no output

cargo build
cargo test

I ran into this while wiring openai-harmony into siGit.

The `image` crate is not referenced anywhere in src/ — no `use image`,
no `extern crate image`. However, it transitively depends on:

  image → avif (default features) → ravif → rav1e → bitstream-io → core2

All versions of `core2` were yanked on 2026-04-14, which means any
fresh `cargo build` or `cargo add openai-harmony` now fails with:

  error[E0463]: can't find crate for `core2`

Removing the unused dependency unblocks downstream consumers with no
functional impact.
@setoelkahfi
Copy link
Copy Markdown
Author

Small bump in case this got buried. This PR just removes an unused image dependency that is currently pulling in yanked core2 versions, which breaks fresh downstream installs. If a maintainer has a minute to take a look, I would appreciate it. Thanks.

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.

1 participant