chore: update lance dependency to v6.0.0-beta.7#110
Open
lance-community wants to merge 1 commit intomainfrom
Open
chore: update lance dependency to v6.0.0-beta.7#110lance-community wants to merge 1 commit intomainfrom
lance-community wants to merge 1 commit intomainfrom
Conversation
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
1 participant
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.
Summary:
org.lance:lance-coreto6.0.0-beta.7.lance-namespace-coreandlance-namespace-apache-clientto0.7.2, matching the Lancerefs/tags/v6.0.0-beta.7source POM.LancePageSinkto use the newWriteFragmentBuilder.namespaceClient(...).tableId(...)API for namespace-backed credential refresh.Verification:
refs/tags/v6.0.0-beta.7exists inlance-format/lanceand checked the taggedjava/pom.xmlfor namespace dependency compatibility.make lintpassed.make compilepassed.Note:
org.lance:lance-core:6.0.0-beta.7during this run, so the tagged Lance Java artifact was installed into the runner's local Maven cache from source before running verification.