Release v2.8.0: finish the Mimir -> Mneme rename (URLs, registry metadata)#319
Merged
Conversation
…data) The crate/binary rename merged in #318, but repo-URL references and registry metadata still pointed at the pre-rename repo, since the GitHub repo itself hadn't been renamed yet at PR time. Now that Perseus-Computing-LLC/mimir -> Perseus-Computing-LLC/mneme is done: - Bumped version to 2.8.0 (Cargo.toml/Cargo.lock), added the [2.8.0] CHANGELOG heading (the rename entry was already drafted under [Unreleased]). - Repo URL Perseus-Computing-LLC/mimir -> .../mneme across README, CONTRIBUTING, SUPPORT, docs/, integrations/*, awesome-mimir.md, clawhub/skills/mimir/SKILL.md, plugins/obsidian-mimir/manifest.json. GitHub redirects the old URLs, but these should point at the canonical path now that it exists. - server.json: title, version, OCI image identifier (ghcr.io/perseus-computing-llc/mneme:2.8.0), websiteUrl/repository URL, and the --db packageArgument (mneme.db) updated. Deliberately LEFT UNCHANGED: the "name" field (io.github.Perseus-Computing-LLC/mimir) — that's a GitHub-org ownership-verified identity in the MCP Registry, not a display string; changing it is a registry re-verification action, not a file edit. Also kept the "mimir-data" Docker volume name so existing registry users don't get a silently-empty new volume. - manifest.json (Claude Desktop/MCPB extension): name, version, display_name, urls, entry_point, and mcp_config updated to mneme. Pushing this to main re-triggers the Docker workflow under the new repository name, producing ghcr.io/perseus-computing-llc/mneme images (the merge of #318 happened before the repo rename, so it pushed to the old ghcr.io/.../mimir package instead). 113/113 tests pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Jul 1, 2026
tcconnally
added a commit
that referenced
this pull request
Jul 1, 2026
Code identifiers, GHCR image, repo URLs, and registry metadata were already renamed in #318/#319. This pass covers the product-name prose still saying "Mimir" in awesome-mimir.md, CONTRIBUTING.md, SUPPORT.md, SBOM/federal-buyers/EXPORT-CONTROL docs, the three MCP client integration guides, the three vs-competitor comparison docs, and the four integrations/ READMEs. Deliberately left "mimir"/"Mimir" where it's a real back-compat identifier rather than prose: - mimir_* MCP tool wire names (unchanged, back-compat guaranteed) - ~/.mimir/data/mimir.db path examples (unchanged, back-compat path) - The CLI binary invocation and "mcpServers": {"mimir": {"command": "mimir", ...}} config key — install.sh symlinks mneme -> mimir, so "mimir" is still the primary working command today - PyPI package/module names and classes (mimir_autogen, mimir_crewai, mimir_langgraph, mimir-persist, MimirStore, MimirMemoryTool, MimirMemory) and their real "binary=\"mimir\"" code defaults - docs/SBOM.md's literal crate/component identifiers (crates.io:mimir@2.0.0, Component name: mimir) - External repo name (hermes-mimir-plugin) and this repo's own filenames (awesome-mimir.md, mimir-vs-*.md) Co-authored-by: tcconnally <hermes@perseus.observer> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
Follow-up to #318 (the crate/binary rename) now that the GitHub repo itself has been renamed
Perseus-Computing-LLC/mimir->Perseus-Computing-LLC/mneme.server.json: title/version/OCI image identifier (ghcr.io/perseus-computing-llc/mneme:2.8.0)/URLs/--dbarg updated. Deliberately left unchanged: the"name"field (io.github.Perseus-Computing-LLC/mimir) — that's an MCP Registry ownership-verified identity, re-verifying it is a registry-side action, not a file edit. Also kept themimir-dataDocker volume name so existing registry pulls don't silently get an empty new volume.manifest.json(Claude Desktop/MCPB extension): name/version/display_name/urls/entry_point/mcp_config updated to mneme.Merging this re-triggers the Docker workflow under the renamed repo, producing
ghcr.io/perseus-computing-llc/mnemeimages — the #318 merge happened just before the repo rename, so it pushed to the oldghcr.io/.../mimirpackage instead.Test plan
cargo +stable-x86_64-pc-windows-msvc test --release— 113/113 passed.v2.8.0to produce semver-tagged GHCR images and cut the GitHub Release.🤖 Generated with Claude Code