Repository navigation
release: Memmy v1.2.401 - #729
Draft
syzsunshine219 wants to merge 46 commits into
Draft
syzsunshine219 wants to merge 46 commits into
syzsunshine219 wants to merge 46 commits into
Conversation
…tion-v126 fix(edit_file): 前置定位模式校验并明确参数互斥规则
local-scanner.ts loaded ignore through createRequire(import.meta.url), which the runtime bundler cannot follow. ignore was neither bundled nor copied as an external package, so the packaged Memory server crashed on startup with: Cannot find module 'ignore'. A static import lets the bundler include it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix: bundle ignore into the Memory runtime package
…-v1.2.4 chore: apply eMudhra runtime upgrade to release v1.2.4
Synchronize the main branch to the v1.2.401 branch
better-sqlite3 13 ships N-API prebuilds under prebuilds/<platform>-<arch>.node and no longer produces build/Release/better_sqlite3.node, so verifyRuntimeDependencies failed with "better-sqlite3 native module is missing" for every target. Check the prebuild for the target instead and drop the now-unused findFiles helper. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…heck fix: check the better-sqlite3 13 prebuild in the Memory runtime package
fix memory panel pagination and skill usage analytics
lipo requires the executable before -verify_arch, so the reversed call rejected every downloaded update and the settings page reported an install failure. Co-authored-by: Cursor <cursoragent@cursor.com>
Collaborator
Author
|
Project Harness review handoff marker. Only reviews submitted strictly after this GitHub timestamp qualify. |
Zy memmate unified approval
Collaborator
Author
|
Project Harness review handoff marker. Only reviews submitted strictly after this GitHub timestamp qualify. |
…c updates codesign treats a -R value without a leading equals sign as a filename, and the certificate OID needs the field. prefix, so a signed update failed the identity check after the architecture check. Co-authored-by: Cursor <cursoragent@cursor.com>
fix: compare update versions in character order
This branch has not been deployed
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.
Refresh the v1.2.401 release candidate to
9ff07878a9628f30984dfd9e0a5ee4a809c5a3d2onrelease/v1.2.401, targetingmain@74b26fc78ebd14a784981ba8e83bebf878c20865.The latest branch changes enforce MemMate-managed file permissions and approved traversal/search, isolate managed state, validate file edits, and support approved PDF/DOCX text access. Desktop updates also compare version characters consistently and pass a literal Developer ID requirement when staging Mac updates. Existing Windows packaging changes and release documentation remain part of this release candidate.
The first Full run on
3a5cf295passed 12 checks and reproduced TS2339 in the new managed-state regression:ToolRegistry.get()returns the baseToolinterface, which does not declareworkspace. This refresh preserves the tool-existence and exact workspace assertion withtoHaveProperty, without widening the production interface. It also adds the newly merged behavior to both release-note files.Verified on this candidate:
Verify this candidate's Harness Full result and evidence fingerprint in its content-bound Harness handoff on this PR. Historical handoff records describe their own source SHA and must not be reused for this candidate. Qizhu's reporting endpoint is https://qcp.memtensor.cn; only a parsed server receipt matching the sealed run/attempt and export digest counts as acceptance. A local queue entry is not a server receipt, and uploaded collect-only evidence is not release approval.
Release review blockers still open:
scripts/internal/win/build-nsis.sh,verify_packaged_windows_unpacked_artifacts).run_electron_builder_with_signing_recovery).release/v1.2.4; no exact package source SHA/build manifest was available. Source regression success does not prove those packages match this candidate.Keep this PR Draft for independent maintainer review. Merge, tag, package-source attestation and formal publication remain separate release steps.