Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Bumps the MemPalace package version to v3.2.0 in the Python packaging metadata.
Changes:
- Update
[project].versioninpyproject.tomlfrom3.1.0to3.2.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| [project] | ||
| name = "mempalace" | ||
| version = "3.1.0" | ||
| version = "3.2.0" |
There was a problem hiding this comment.
The project version was bumped here, but the codebase still has other version sources (e.g., mempalace/version.py exports __version__ = "3.1.0", README badge, integration manifests). This will cause a mismatch between the published package metadata (3.2.0) and the runtime-reported version. Please update the other version references as part of the bump, or switch to a single-source version setup (e.g., have the build read from mempalace/version.py) to prevent future drift.
igorls
added a commit
that referenced
this pull request
Apr 13, 2026
PR #761 bumped pyproject.toml to 3.2.0 but missed three other version strings, causing test_version_consistency to fail on develop CI (macos, linux 3.11, windows). - mempalace/version.py: 3.1.0 → 3.2.0 (unblocks test_version_consistency) - README.md: version badge shield 3.1.0 → 3.2.0 - integrations/openclaw/SKILL.md: 3.1.0 → 3.2.0 - CHANGELOG.md: rename [Unreleased] → [3.2.0] — 2026-04-13, add entries for #685, #690, #707, #716, #734, #755, #757, #761 Verified locally: 689/689 tests pass, ruff clean.
mvalentsev
added a commit
to mvalentsev/mempalace
that referenced
this pull request
Apr 13, 2026
version.py was left at 3.1.0 after the v3.2.0 bump in pyproject.toml (MemPalace#761), breaking test_version_consistency on every PR targeting develop. pyproject.toml project URLs still pointed at the old milla-jovovich GitHub org instead of MemPalace.
mvalentsev
added a commit
to mvalentsev/mempalace
that referenced
this pull request
Apr 13, 2026
version.py was left at 3.1.0 after the v3.2.0 bump in pyproject.toml (MemPalace#761), breaking test_version_consistency on every PR targeting develop. pyproject.toml project URLs still pointed at the old milla-jovovich GitHub org instead of MemPalace.
mvalentsev
added a commit
to mvalentsev/mempalace
that referenced
this pull request
Apr 13, 2026
version.py was left at 3.1.0 after the v3.2.0 bump in pyproject.toml (MemPalace#761), breaking test_version_consistency on every PR targeting develop. pyproject.toml project URLs still pointed at the old milla-jovovich GitHub org instead of MemPalace.
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
jphein
added a commit
to jphein/mempalace
that referenced
this pull request
Apr 13, 2026
Upstream bumped pyproject.toml to 3.2.0 in MemPalace#761 but missed version.py. Aligns the two so test_version_consistency passes. Co-Authored-By: Claude Opus 4.6 <[email protected]>
gavinmcfall
added a commit
to gavinmcfall/mempalace
that referenced
this pull request
Apr 13, 2026
Resolves pre-existing upstream inconsistency where commit 6614b9b (bump version v3.2.0 MemPalace#761) updated pyproject.toml but not version.py, breaking tests/test_version_consistency.py.
sha2fiddy
pushed a commit
to sha2fiddy/mempalace
that referenced
this pull request
Apr 13, 2026
PR MemPalace#761 bumped pyproject.toml to 3.2.0 but missed three other version strings, causing test_version_consistency to fail on develop CI (macos, linux 3.11, windows). - mempalace/version.py: 3.1.0 → 3.2.0 (unblocks test_version_consistency) - README.md: version badge shield 3.1.0 → 3.2.0 - integrations/openclaw/SKILL.md: 3.1.0 → 3.2.0 - CHANGELOG.md: rename [Unreleased] → [3.2.0] — 2026-04-13, add entries for MemPalace#685, MemPalace#690, MemPalace#707, MemPalace#716, MemPalace#734, MemPalace#755, MemPalace#757, MemPalace#761 Verified locally: 689/689 tests pass, ruff clean.
sha2fiddy
pushed a commit
to sha2fiddy/mempalace
that referenced
this pull request
Apr 14, 2026
PR MemPalace#761 bumped pyproject.toml to 3.2.0 but missed three other version strings, causing test_version_consistency to fail on develop CI (macos, linux 3.11, windows). - mempalace/version.py: 3.1.0 → 3.2.0 (unblocks test_version_consistency) - README.md: version badge shield 3.1.0 → 3.2.0 - integrations/openclaw/SKILL.md: 3.1.0 → 3.2.0 - CHANGELOG.md: rename [Unreleased] → [3.2.0] — 2026-04-13, add entries for MemPalace#685, MemPalace#690, MemPalace#707, MemPalace#716, MemPalace#734, MemPalace#755, MemPalace#757, MemPalace#761 Verified locally: 689/689 tests pass, ruff clean.
igorls
added a commit
that referenced
this pull request
Apr 14, 2026
Main had 9 commits that never back-merged into develop after the v3.2.0 release cycle. Resolving conflicts as follows: - mempalace/version.py: keep develop (3.3.0 release target) - README.md: keep develop (Milla's #835 audit is authoritative — main had stale 19 tools / 170 tokens / "30x lossless" / v3.0.0 label) - hooks/mempal_{save,precompact}_hook.sh: keep develop (#786 reversed the #666 "decision=block" behavior intentionally to stop hooks from making agents write in chat) - pyproject.toml: auto-merged — keeps develop's 3.3.0 and picks up main's chromadb upper-bound removal (#690) - CONTRIBUTING.md, mempalace/hooks_cli.py: auto-merged cleanly — picks up main's improvements (fork-first clone, more detailed block reason strings that name MemPalace and specific tools) - integrations/openclaw/SKILL.md: bumped 3.2.0 → 3.3.0 (version tracks the package per #761 convention) - CHANGELOG.md: manual merge — kept develop's preamble + Unreleased v3.3.0 section + footer links; folded main's richer v3.2.0 entries (Packaging section for #690/#761; Bug Fixes #685/#677/#716/#707/ #755/#757; Documentation #734/#733) into the v3.2.0 section; deduped the split Documentation sections that auto-merge produced
This was referenced Apr 14, 2026
Merged
igorls
added a commit
that referenced
this pull request
Apr 14, 2026
Bring back the main-only content that develop has been missing: - pyproject.toml chromadb upper-bound removal (#690) - CHANGELOG [3.2.0] Packaging subsection (#690, #761) - CONTRIBUTING.md fork-first clone instructions - mempalace/hooks_cli.py richer block-reason strings (from #666, still used by the Python hook invocation path) - integrations/openclaw/SKILL.md version bump to 3.3.0 Plus the v3.3.0 release commit itself (4aa7e1e) and the legacy main-only commits (#666, #690, v3.2.0 finalization) for history. Resolves the main → develop drift that caused PR #838's conflicts. Going forward, back-merging main to develop after each release will prevent the same pattern. Single conflict in CHANGELOG.md resolved by taking main's version (the Packaging subsection under [3.2.0]).
3 tasks
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.
No description provided.