Merged
Conversation
Why these changes are being introduced: The shift to elevating dataset metadata as an expected and required asset, and utilizing DuckDB context's for metadata and data retrieval is a sizable and breaking change. Feels like this warrants a major version bump. How this addresses that need: * Bumps internal library version to 3.0 Side effects of this change: * `make update` commands from TIMDEX components will pickup this new version Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/TIMX-537
Pull Request Test Coverage Report for Build 16975786385Details
💛 - Coveralls |
ehanson8
approved these changes
Aug 14, 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.
Purpose and background context
Why these changes are being introduced:
The shift to elevating dataset metadata as an expected and required asset, and utilizing DuckDB context's for metadata and data retrieval is a sizable and breaking change. Feels like this warrants a major version bump.
How this addresses that need:
Includes new or updated dependencies?
NO
Changes expectations for external applications?
YES:
make updatecommands from TIMDEX components will pickup this new versionWhat are the relevant tickets?