chore: sync main into develop after v0.4.0 release#59
Closed
fvadicamo wants to merge 2 commits into
Closed
Conversation
- Optional enrollment mode for LMS integrations (FEAT-003) - Widget UX: collapsible sources, a11y, i18n, snippet fix - Phase 2 stabilization: BUG-010, BUG-011, DEBT-002/003/008 - Sync main history, 3 critical bug fixes from v0.2.0 review - Version 0.3.0, CHANGELOG, docs update (18 new config vars, ERR-LEARN codes) - Commit signing guide, quality gate, branching rules in CONTRIBUTING Reviews: PRs #42-#47, 30+ comments addressed (CodeRabbit, Gemini) Tests: 576 passed, integration + NFR gates green Refs: FEAT-003, BUG-010, BUG-011, DEBT-002, DEBT-003, DEBT-008
- Configurable grounding mode strict/hybrid with per-namespace override (FEAT-020) - QueryTrace persistence for all pipelines, streaming and non-streaming (BUG-013) - Reranker scores, eval mode tracing, debug query logging (DEBT-014, DEBT-015, DEBT-009, FEAT-019) - Safeguard bypass fix in hybrid mode, XML escaping, config constraints (PR #57) - Production-ready chatbot widget, RAG prompt restructure, conversation persistence - CI: remove latency step requiring LLM (PR #58) Reviews: 21 inline + 3 outside-diff addressed (CodeRabbit, Gemini, github-code-quality) Tests: all passing, 28/28 CI checks green Refs: PRs #49-#58, milestone v0.4.0
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Contributor
Author
|
Not needed: main and develop have identical file content after v0.4.0 release. Back-merge is only necessary when there are hotfixes on main that develop doesn't have. In this case all work went through develop, so history alignment happens naturally at the next release merge. |
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.
What
Back-merge main into develop after v0.4.0 release (PR #56).
Why
Keeps histories aligned. Without this, the next release PR (develop -> main) sees diverged merge commits and may produce spurious conflicts (same issue that caused PR #45 after v0.2.0).
Details
Zero file changes. Only merge commits from main (#44, #56) are incorporated into develop's history.