Update dependency versions#26
Merged
brokkoli71 merged 1 commit intozarr-developers:mainfrom Oct 6, 2025
Merged
Conversation
normanrz
approved these changes
Oct 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR bumps the dependency versions to the latest available:
Or are there particular reasons to keep older versions?
For aws-skd v1 to v2 I used the migration tool mentioned https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/migration-tool.html . Tests are passing. But I'm not sure if the tests cover everything which is affected by this PR.
Background: I'd like to use zarr-java in ZarrReader and omero-zarr-pixel-buffer but struggle with dependency/version conflicts. So updating all to use the latest versions would hopefully solve this.