chore: bump dakera-client to v0.11.100 (smart_score fix, DAK-7328) - #155
Merged
Conversation
RecalledMemory.score now resolves smart_score ?? weighted_score ?? score, matching server ranking order. Exposes optional smart_score + weighted_score fields on RecalledMemory. Co-Authored-By: Paperclip <noreply@paperclip.ing>
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.
Summary
Version bump for the smart_score ranking fix landed in PR #154.
dakera-clientfrom0.11.99→0.11.100.scoresemantic changeChange Details
Breaking-ish fix:
.scoreonRecalledMemorypreviously returned rawscore. It now returnssmart_score ?? weighted_score ?? score, matching the server's actual ranking order. Consumers sorting by.scorewill now see results in the correct server-rank order. New optional fieldssmart_scoreandweighted_scoreare exposed for consumers that need the raw components.Related: #154