libvips drift: pinned versions are behind upstream
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
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Stirling-Tools/JPDFium
-
pdfium-drift
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Stirling-Tools/JPDFium#299 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
Stirling-Tools/JPDFium#280 ·
Maintainers usually reply within 1 day
-
Split up some of the bridge files, as their sizes are getting out of handPossibly taken @balazs-szucs claimed this 2 days ago. Open
Stirling-Tools/JPDFium#279 · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
Stirling-Tools/JPDFium#276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Stirling-Tools/JPDFium#192 ·
Maintainers usually reply within 1 day
All issues in Stirling-Tools/JPDFium
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/skywalking#14239 ·
Maintainers usually reply within 1 day
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Possibly taken @dbusche claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
h2database/h2database#4580 ·
Maintainers usually reply within 1 day
-
hermes-queue
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Maintainers usually reply within 1 day
-
Guidelines: document how to build a use case against a local, unpublished Flow/browserless-test changePossibly taken @totally-not-ai claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
vaadin/use-cases#452 · 1 comment ·
Maintainers usually reply within 1 day
-
area/storage area/storage/sql
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Apicurio/apicurio-registry#11159 ·
Maintainers usually reply within 1 day