Repository navigation
chore(release): v1.4.2 - #488
Closed
gloryfromca wants to merge 1 commit into
Closed
gloryfromca wants to merge 1 commit into
gloryfromca wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Member
Author
|
Holding the release: more code lands on main first. Will reopen a fresh release PR when it is time. |
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
Cut 1.4.2: the index-key fix (#481) with its follow-ups (#487) and the knowledge category fix (#469). Version bump, regenerated
docs/openapi.json, and the CHANGELOG's Unreleased entries moved under## [1.4.2]with the release page's lead paragraph and### Upgradegroup (LanceDB: nothing to do; Milvus: one rebuild; the two LanceDB roots that need a command).Area
Verification
Checklist
main..envfiles, dependency folders, or generated output.Notes for Reviewers
git tag -a v1.4.2 -m v1.4.2 && git push origin v1.4.2, approve thereleaseenvironment in the Actions run, verify https://pypi.org/project/everos/1.4.2/, then publish the drafted GitHub Release page (its body is lifted from this CHANGELOG section).🤖 Generated with Claude Code