[PR #6860] checkpoint/memory: align latest semantics across get_tuple and list #5357

Open
opened 2026-02-20 17:51:35 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/langchain-ai/langgraph/pull/6860

State: open
Merged: No


Problem

Checkpoint callers can observe inconsistent "latest/current" behavior between tuple and list surfaces, which breaks deterministic operator expectations.

Why now

Issue #6821 captured active semantic drift across API surfaces.

What changed

  • InMemorySaver.get_tuple() now selects latest checkpoint by insertion order, not lexicographic checkpoint id.
  • Added/updated tests that assert aligned latest behavior and list limit semantics.

Validation

  • make format
  • make lint
  • TEST=tests/test_memory.py make test
  • make test

Refs #6821

**Original Pull Request:** https://github.com/langchain-ai/langgraph/pull/6860 **State:** open **Merged:** No --- ## Problem Checkpoint callers can observe inconsistent "latest/current" behavior between tuple and list surfaces, which breaks deterministic operator expectations. ## Why now Issue #6821 captured active semantic drift across API surfaces. ## What changed - `InMemorySaver.get_tuple()` now selects latest checkpoint by insertion order, not lexicographic checkpoint id. - Added/updated tests that assert aligned latest behavior and list limit semantics. ## Validation - `make format` - `make lint` - `TEST=tests/test_memory.py make test` - `make test` Refs #6821
yindo added the pull-request label 2026-02-20 17:51:35 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraph#5357