Release mnemostack 1.3.0 - #133
Merged
Merged
Conversation
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
1.2.0to1.3.02026-07-27Release scope
This is a minor release because the changes merged after
1.2.0add public, backward-compatible functionality: configurable multi-field lexical arms, per-field fusion weights, named retriever arms, and corresponding CLI, MCP, HTTP, diagnostics, and CI behavior.Validation
pytest -q— 1495 passed, 10 skippedruff check .mypy srcpython -m buildtwine checkon both the wheel and sdistmnemostack.__version__, andmnemostack --versionall report1.3.0Audit
Re-read the release diff independently after validation, including version-source drift, changelog placement/date, package metadata, unintended tracked build artifacts, and release-scope regressions. The audit found no behavioral or security changes in this release-only diff. The added changelog-version regression test guards the release metadata invariant that was previously checked only manually.
This PR does not create a tag, GitHub Release, or PyPI publication.