Repository navigation
Conversation
alt-glitch
added
type/bug
PR #98527 — fix(memory): align Hindsight client pin at 0.9.2Summary: Bumps Non-blocking observations:
Verdict: Clean coordinated pin bump. No blocking issues. |
teknium1
added a commit
that referenced
this pull request
Sep 22, 2026
…mes list-typed files and reads hooks: - hindsight-client==0.6.1 / mem0ai==2.0.10 exact pins made _is_satisfied() reject every newer compatible release, so hermes update kept downgrading a working client and broke embedded daemons whose DB a newer client had migrated (#86992, #39424, #98407, #99317). The lazy entries now mirror the plugin manifests (>=0.6.1,<1 and >=2.0.10,<3); pyproject extras stay the floor install. Slim redo of #99557 (nateEc) / #98416 / #98527 (ttomiczek) / #39754. - A list-typed plugin.yaml is refused with "top level must be a mapping" instead of an AttributeError swallowed as "Failed to parse" (#14066, discovery side). - ``hooks:`` (the spelling bundled manifests carried) still populates provides_hooks (#108371).
teknium1
added a commit
that referenced
this pull request
Sep 22, 2026
…mes list-typed files and reads hooks: - hindsight-client==0.6.1 / mem0ai==2.0.10 exact pins made _is_satisfied() reject every newer compatible release, so hermes update kept downgrading a working client and broke embedded daemons whose DB a newer client had migrated (#86992, #39424, #98407, #99317). The lazy entries now mirror the plugin manifests (>=0.6.1,<1 and >=2.0.10,<3); pyproject extras stay the floor install. Slim redo of #99557 (nateEc) / #98416 / #98527 (ttomiczek) / #39754. - A list-typed plugin.yaml is refused with "top level must be a mapping" instead of an AttributeError swallowed as "Failed to parse" (#14066, discovery side). - ``hooks:`` (the spelling bundled manifests carried) still populates provides_hooks (#108371).
Collaborator
|
Thanks @ttomiczek — instead of bumping the exact pin (already stale vs PyPI), the lazy entry now mirrors the manifest range Superseded by #118841 (merge 74f726c), which credits this PR. Closing. |
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
5 participants
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
Updates Hermes's Hindsight client from the stale
0.6.1pin to the reviewed0.9.2release across every enforcement path:hindsightoptional dependency and committeduv.lockmemory.hindsightintools/lazy_deps.pyexclude-newerexemption required to resolve this exact reviewed release immediatelyAdds a regression test covering the pin, lock resolution, and
exclude-newerexemption.This prevents normal updates and lazy dependency healing from restoring the obsolete 0.6.1 client after an operator has moved to the 0.9.x Hindsight stack.
Verification
Refs #86992