Skip to content

Record the bumps that landed between the tier work and the tag #117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tonytonycoder11 merged 1 commit into from
Aug 6, 2026
Merged

Record the bumps that landed between the tier work and the tag #117

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,6 +147,12 @@ it means for a klib. A degraded cluster reports itself. And there is a binary.
- The release workflow builds the CLI binaries on two runners, proves each against a real Qdrant, and
attaches them to the GitHub Release with SLSA provenance and checksums.
- The benchmarks workflow exposes Qdrant's gRPC port, because the official client speaks it.
- Dependency and action bumps that landed between the tier work and the tag: Ktor 3.5.1 to 3.5.2,
langchain4j 1.18.0 to 1.18.1, Guava 33.5.0 to 33.6.0, and `io.qdrant:client` 1.15.0 to 1.18.3, which
is a benchmark dependency and reaches no published POM. Two GitHub Actions moved by a major:
`actions/attest-build-provenance` v3 to v4 and `actions/download-artifact` v7 to v8, both in
`release.yml`. A grouped minor or patch bump with green CI needs no entry; a major does, and a
workflow that ships no API still decides how this project releases.


## [2.1.0] - 2026-08-02
Expand Down