Feature-heavy release with zero negative reactions, but a Milvus duplicate-chunk bug and search race condition warrant caution for knowledge-base users.
✓ No breaking changes or dangerous deprecations detected for this release.
### Before Submitting - [x] I searched open and closed issues and discussions for an existing report. - [x] I reproduced this bug on the latest release AND on the current `dev` br...
### Before Submitting - [x] I searched open and closed issues and discussions for an existing report. - [x] I reproduced this bug on the latest release AND on the current `dev` br...
### Before Submitting - [ ] I searched open and closed issues and discussions for an existing report. - [ ] I reproduced this bug on the latest release AND on the current `dev` br...
### Before Submitting - [x] I searched open and closed issues and discussions for an existing report. - [x] I reproduced this bug on the latest release AND on the current `dev` br...
### Before Submitting - [x] I searched open and closed issues and discussions for an existing report. - [x] I reproduced this bug on the latest release AND on the current `dev` br...
### Before Submitting - [x] I searched open and closed issues and discussions for an existing report (closest is #17088, a different `None` limit path fixed in 0.6.23; this one is...
### Before Submitting - [x] I searched open and closed issues and discussions for an existing report. - [x] I reproduced this bug on the latest release AND on the current `dev` br...
### Before Submitting - [x] I searched open and closed issues and discussions for an existing report. - [x] I reproduced this bug on the latest release AND on the current `dev` br...
### Before Submitting - Searched open and closed issues and discussions: nothing found. - Checked against the 0.13.0 release (not the dev branch). - Not a security issue. ### Prob...
### Before Submitting - Searched open and closed issues and discussions: nothing found. - Checked against the 0.13.0 release (not the dev branch). - Not a security issue. ### Prob...
If v0.13.0 breaks your environment, revert container image tag to previous stable release: