use newer docker for linux release artifacts#393
Merged
Conversation
ihnorton
approved these changes
Jan 14, 2026
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
2 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.
Releases still fail because of:
Linux Docker build fails to create linux artifacts resulting in empty jars and lining errors.
This PR keeps the docker build in the CI but updates to a newer image to fix the problem and maintain as much backwards compatibility as possible.
https://github.com/TileDB-Inc/TileDB-Java/actions/runs/20881432317/job/60267174700#step:4:505
here is a test run that confirms the fix https://github.com/TileDB-Inc/TileDB-Java/actions/runs/20970018910/job/60271073767. This test run was made by a modified branch to only test that part of the workflow