chore(release): v0.16.0 - #22
Merged
Merged
Conversation
Minor rather than patch: #21 changes a default (embed_missing false -> true) and turns embed_missing=false into a hard error, so callers that passed it explicitly see behaviour change rather than a silent fix. Keeps the tag and the binary's --version in agreement -- the workbench update check compares recorded versions against the payload manifest, so a release whose binary reports a different number is a provenance trap.
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.
Version bump so the v0.16.0 tag and
frg --versionagree.Minor rather than patch: #21 flips the
embed_missingdefault and makesembed_missing=falsea hard error, so any caller that passed it explicitly gets a behaviour change, not a silent fix.Releases here are tag-driven and the workflow does not validate the tag against the crate version — so without this, a
v0.16.0release would ship a binary reporting0.15.0. The workbench update check compares recorded versions against the payload manifest, which makes that a provenance trap rather than cosmetic.Verified:
frg --version->frg 0.16.0.Needed so ferrosa-workbench can pin a forge release carrying the embedding fix (#21) and finally prove semantic search end to end.