chore: back-merge main into dev (v0.6.8 closure)#129
Merged
Conversation
Promote dev → main for the v0.6.8 stable release. Fix (#127): the per-model regex output filter now strips artifact-only replies to empty — the empty-result fail-safe is removed (it leaked the raw `[...]` artifact), whitespace-only strip results collapse to empty, and the LLM output_filter is skipped when the strip empties the reply (so a rewrite pass can't resurrect a bubble). No content bubble reaches the client; the row persists empty content; the audit is kept (pre_filter_content = raw, filter_model = "<regex>"). Version bump 0.6.8-dev -> 0.6.8: 4 Cargo.tomls (workspace + core/llm/store pins), Cargo.lock, openapi.json (info.version 0.6.8), README docker tags (0.6.7 -> 0.6.8). No database migration, no new HTTP/API surface.
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.
Closes the v0.6.8 release loop: merges
main(released 0.6.8) back intodevso ancestry stays closed (the next dev→main PR won't conflict). Two commits: the merge (version files resolved to the released 0.6.8) +chore(dev): reopen 0.6.9-dev. Diff is just the version bump (Cargo.tomls + Cargo.lock + openapi.json); README docker tag stays at the released 0.6.8. Merge with a merge-commit, NOT squash (per the back-merge convention — preserves the ancestor link).