release: vectors 0.1.6 - #59
Merged
Merged
Conversation
Publishes vectors-router and the two semantic-cache decorator modules, and documents 0.1.5, which shipped without a changelog entry.
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
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 0.1.6. This publishes
vectors-router— which merged after 0.1.5 and is not on Maven Central at any version — along with the two new semantic-cache decorator modules.Contents
New modules
vectors-router(Publish vectors-router to Maven Central #57) — semantic routing by embedding similarityvectors-cache-semantic-spring-ai,vectors-cache-semantic-langchain4j(Semantic caching for Spring AI and LangChain4j, with attribute-scoped lookup #58) — chat decorators that answer from a semantically similar earlier promptSPI
SemanticCachegained entry attributes,CacheFilter,lookupTopK, andsupportsAttributes()Fix
DefaultChatOptions.toString(), which is identity-based, so identical option sets produced different signaturesAlso documents 0.1.5, which shipped without a changelog entry.
Release steps after merge
Per
RELEASING.md:dry_runenableddry_rundisabledMaven Central versions are immutable, so the dry run matters.
Verified locally
spotlessCheck build,complianceCheck,verifyLockfiles,verifyGithubWorkflows,:docs:build— all green.🤖 Generated with Claude Code