libvips drift: pinned versions are behind upstream

Open Beginner friendly
#300 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java, linux, macos
Domain
build-system

Research direction

Start with native/vips-build.env to review the source version pins for libvips, libheif, and aom, then check the Prebuild libvips workflow instructions. After updating the source pins, run that workflow and set native/vips.version to its produced release; rerun the workflow to confirm it completes and closes the issue.

Written by the indexing model from the issue text.

Description

vips-drift

Pinned libvips/codec versions are behind upstream.

  • libvips: pinned v8.18.6, upstream v8.18.7
  • libheif: pinned v1.23.4, upstream v1.23.7
  • aom: pinned v3.15.1, upstream v3.15.3-rc1

Source pins live in native/vips-build.env (used by the Linux/macOS from-source builds and the Windows prebuild); the prebuilt pin lives in native/vips.version.

To fix: bump the pin(s), run the Prebuild libvips workflow (workflow_dispatch, or add the prebuild-vips label to a PR), then set native/vips.version to the produced release. Re-run this workflow to confirm the issue closes itself.

Dominant language
Java
Stars
16
Forks
4
Avg merge
2d 2h
Merged PRs (30d)
56

Getting set up

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 Stirling-Tools/JPDFium

All issues in Stirling-Tools/JPDFium

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.