tiledbsoma 1.14.2 hash-fix #203
Merged
Conversation
This file contains 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
johnkerl
requested review from
gspowley,
jdblischak,
mlin and
Shelnutt2
as code owners
gspowley
approved these changes
Sep 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#202 contained a copy-paste from the pre-check PR #201 of the sha/hash info. I forgot to update to the released hash on 202. This PR fixes that.
I noticed this while testing https://github.com/TileDB-Inc/TileDB-REST-UDF-Docker-Images/pull/721 following our established procedure -- on-image I found
The
1.14.1.post3.dev12177573296needs to be1.14.2.single-cell-data/TileDB-SOMA#3075
[sc-56256]