Tags: qdrant/java-client
Tags
fix: run version compatibility check with the resolved API key creden… …tials (#132) * fix: authenticate version compatibility check with resolved credentials The checkCompatibility health check in Builder.build() used this.callCredentials, which withApiKey() no longer populates since the custom-headers refactor (49e4826, released in 1.18.0): the api key MetadataCredentials are only constructed after the check runs. Against an auth-required server (e.g. Qdrant Cloud) the check therefore ran unauthenticated and logged "Failed to obtain server version", re-introducing #96. Resolve the effective call credentials before running the check and pass them in. Add a regression test asserting the check receives the api key credentials. Fixes #131 * ci: Use actions/checkout v5 to resolve dev-vince/actions-publish-javadoc failure * Apply suggestions from code review Co-authored-by: Anush <mail@anush.sh> * chore: Bump version to v1.18.3 --------- Co-authored-by: Anush <mail@anush.sh>
v1.17.0 (#105) * v1.17.0 Signed-off-by: Anush008 <mail@anush.sh> * chore: Bump to v1.17.0 Signed-off-by: Anush008 <mail@anush.sh> * docs: Updated README.md Signed-off-by: Anush008 <mail@anush.sh> * fix: Use testcontainers/testcontainers-java#10788 (comment) Signed-off-by: Anush008 <mail@anush.sh> --------- Signed-off-by: Anush008 <mail@anush.sh>
chore: Update gRPC and Protoc versions to 1.75.0 and 3.25.5 (#100) * chore: Update gRPC and Protoc versions to 1.75.0 and 3.25.5 Signed-off-by: Anush008 <anushshetty90@gmail.com> * chore: Bump package version Signed-off-by: Anush008 <anushshetty90@gmail.com> --------- Signed-off-by: Anush008 <anushshetty90@gmail.com>
PreviousNext