Repository navigation
After the 26.11.1 engine bump: example 29 on native again, NOTICE refreshed first - #262
Merged
Merged
Conversation
…h the kept NOTICE first The skip of 29_hybrid_memory_retrieval.py waited for engine 26.11.1 (vectorNeighbors where option), which main now links (#258). The release-day steps refreshed ARCADEDB_ENGINE_NOTICE after the first notices regeneration, but gen_notices embeds it, so the 26.11.1 bump needed a second CI round; the refresh now comes first, in release.adoc and in the release issue template. Closes #261 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tae898
added
documentation
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.
Closes #261
Two follow-ups of the dev engine bump to 26.11.1 (#258):
29_hybrid_memory_retrieval.pyruns on the native wheel again (its skip waited for thevectorNeighborswhereoption of engine 26.11.1, whichmainnow links), and the release-day steps refresh the kept engineNOTICEbefore the first notices regeneration instead of after it, inrelease.adocand in the release issue template (the generated notices embed theNOTICE, so the old order cost one more CI round). Checked with pre-commit; the native examples job on this PR runs example 29.🤖 Generated with Claude Code