Release 2.0.0 — Tier 5, Post-1.0 expansion - #66
Merged
Conversation
The release the transport seam was built for. kdrant-transport-grpc is an opt-in gRPC engine behind the same QdrantClient, and kdrant-core compiles for the JVM and eight Kotlin/Native targets. Adding a second engine changed no line of kdrant-core, which is the claim the seam has been making since the first release and the only way to test it was to write one. The major bump is for the artifact layout and not for the API. The JVM public API is unchanged byte for byte — apiCheck reports no diff against 1.2.0. kdrant-core's JVM classes moved to kdrant-core-jvm because the module is multiplatform now: a Gradle build changes only the version number, a Maven build naming kdrant-core has to move. Three entries were missing from [Unreleased] and are recorded here rather than lost: release notes generated from the changelog, linked artifacts for the published jars, and the set of artifacts the provenance attestation covers now being derived from the build. That last one was a hardcoded list that stopped covering a module the day the gRPC engine arrived, with nothing going red — so it derives from which modules publish, anchored on the block rather than the word, because the testkit's build file explains in a comment that it has no publishing block and an unanchored match attests it for saying so.
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.
Cuts
2.0.0. Tier 5 is complete: #52 (opt-in gRPC engine) and #23 (multiplatform core) both merged, andthe milestone has no open issues.
The major bump is for the artifact layout, not the API.
apiCheckreports no diff against1.2.0— the JVM public API is unchanged byte for byte.kdrant-core's JVM classes moved tokdrant-core-jvmbecause the module is multiplatform now, so a Gradle build changes only the versionnumber and a Maven build naming
kdrant-corehas to move. That is written up underUpgrading from
1.x.Three entries were missing from
[Unreleased]and are recorded rather than lost, underInternal:release notes generated from the changelog, linked artifacts for the published jars, and the derived
attestation set below.
The attested artifact set now derives from the build. It was a hardcoded list in
release.yml, andit stopped covering a module the day the gRPC engine arrived with nothing going red — which is the
failure mode that matters. It now walks the modules that publish. The match is anchored on
^mavenPublishing {rather than the word:kdrant-testkit's build file explains in a comment that itcarries no publishing block, and an unanchored grep attests it for saying so.
compgenfinds no jar forthe BOM, which is how a module with nothing to attest drops out.
Checks run:
./gradlew build apiCheckgreen, library audit At standard.###headings in the new section.awkextraction produces a non-empty body for2.0.0.[Unreleased]left empty above the new heading.After merge: annotated tag
v2.0.0naming the tier, then the board's #52 and #23 flip toShippedandthe Tier 5 milestone closes.