× smfs.
Star on GitHub
← Back to runs
Claude Code Claude Code Codex Codex
dp_006 q06 100 files multi_hop Claude Code

The v0.5.0 release notes state that v0.4.2 was yanked from crates.io. But the May 2026 retro and issue #89 give different dates for the yank. What date does each source give, and what is the most precise reconciliation of the timeline?

Gold answer

The May 2026 retro (retro-may-2026.md) states 'v0.4.2 was yanked from crates.io on 2026-05-27'. Issue #89 shows @svenh asked for a yank on 2026-05-26 and @lior-bz responded 'Yanked. crates.io banner now reads: kitabi 0.4.2 yanked: ABI break, see #89.' in a comment dated 2026-05-27. The v0.5.0 release notes state 'v0.4.2 was yanked from crates.io on 2026-06-01', which contradicts both other sources. The most precise reconciliation: the yank happened on 2026-05-27 per the retro and per the issue thread timestamp; the 2026-06-01 date in the release notes appears to be an error (possibly when the release notes were drafted rather than when the yank occurred).

Filesystem View raw JSON
Input
422k
Output
586
Steps
12
Tools
6
Latency
48.4s
Cost
$6.37
#2 Ran ls /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/ 50 chars
Command Bash 
ls /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/

{
  "description": "List agent_memory contents"
}
Result 7 lines 
code
email
issues
memory
notes
pr_threads
releases
#3 Ran ls /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/releases/ /Users/prasanna/Docum… 1,980 chars
Command Bash 
ls /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/releases/ /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/issues/ /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/notes/

{
  "description": "List relevant subdirectories"
}
Result 9 lines 
/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/issues/:
issue-008-md-table-alignment-bug.md
issue-014-empty-heading-levels.md
issue-019-windows-line-endings.md
issue-027-pandoc-attributes-declined.md
issue-031-asciidoc-include-directive.md
issue-036-tokio-runtime-panic-macos.md
issue-041-performance-regression-50mb.md
issue-045-emoji-in-he…
#4 Ran ls /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/releases/ | grep -i "0.4" 28 chars
Command Bash 
ls /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/releases/ | grep -i "0.4"

{
  "description": "Find v0.4.2 release file"
}
Result 1 lines 
release-v0.4.0-2026-05-15.md
#6 Edited agent_memory/releases/release-v0.5.0-2026-06-08.md 15,908 chars
Command Read 
{
  "file_path": "/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/releases/release-v0.5.0-2026-06-08.md"
}
Result 9 lines 
1	# kitabi v0.5.0 (2026-06-08) — Concurrent file processing
2	
3	> **Breaking change:** plugin-API ABI version bumped from 1 → 2. Plugin authors must rebuild against `kitabi-plugin-api` 0.5.x. See [CHANGELOG-PLUGIN-API.md](../../CHANGELOG-PLUGIN-API.md) and the migration section below.
4	
5	---
6	
7	## Highlights 🚀
8	
9	- **5× throughput improvement** on multi-file batches. A 60 MB Wikipedia subs…
#8 Ran grep -n -i "yank\|0.4.2" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/issues/is… 5,750 chars
Command Bash 
grep -n -i "yank\|0.4.2" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/issues/issue-089-plugin-api-break.md /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/notes/retro-may-2026.md

{
  "description": "Find yank dates in issue #89 and May retro"
}
Result 2 lines 
/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/issues/issue-089-plugin-api-break.md:1:# Plugin API breaks between v0.4.1 and v0.4.2 (silent ABI change)
/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/issues/issue-089-plugin-api-break.md:8:- **Affected versions:** v0.4.2 (yanked 2026…
#10 Edited agent_memory/issues/issue-089-plugin-api-break.md 14,197 chars
Command Read 
{
  "file_path": "/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/issues/issue-089-plugin-api-break.md"
}
Result 8 lines 
1	# Plugin API breaks between v0.4.1 and v0.4.2 (silent ABI change)
2	
3	**Issue #89** · `bug` `plugin-api` `regression` `breaking`
4	
5	- **Opened:** 2026-05-26 by @svenh
6	- **Closed:** 2026-06-08 by @lior-bz (alongside the v0.5.0 release)
7	- **Resolution:** revert the offending signature change in v0.4.3 + add an ABI-version assertion in the loader (shipped in v0.5.0)
8	- **Affected ver…
#12 Reasoning 1,911 chars 
## Dates by source

| Source | Date given | Where |
|---|---|---|
| v0.5.0 release notes | **2026-06-01** | release-v0.5.0-2026-06-08.md:169 ("A note on v0.4.2") |
| Issue #89 header | **2026-05-27** | issue-089-plugin-api-break.md:8 ("Affected versions") |
| Issue #89 thread | **2026-05-27** | issue-089-plugin-api-break.md:159–163 — Lior posts the "Yanked. crates.io banner now reads…" comment dated 2026-05-27 |
| May 2026 retro | **2026-05-27** | retro-may-2026.md:63 |

A small correction to the question's premise: the May retro and issue #89 actually **agree** (both say 2026-05-27). The outlier is the v0.5.0 release notes, which say 2026-06-01.

## Most precise reconciliation

The yank happened on **2026-05-27**. That date is corroborated by:

1. The contemporary comment in issue #89 where Lior posts the crates.io yank banner, dated 2026-05-27 (preceded by his 2026-05-26 commitment to "yank tomorrow morning CET").
2. Drift's "Yank was the right call" reply also dated 2026-05-27.
3. The May retro, written closer to the events than the v0.5.0 notes.

The v0.5.0 release notes' **2026-06-01** appears to be a write-up error. Looking at the issue #89 timeline, 2026-06-01 is the date Lior commented that the **ABI assertion** landed on the v0.5 branch (commits 4a9b210 and 1c8fe33) — line 187 of issue #89. The release-notes pass two months later seems to have conflated "assertion-landed-on-v0.5-branch" (2026-06-01) with "v0.4.2 yanked from crates.io" (2026-05-27).

### Reconstructed tight timeline

- 2026-05-23 — v0.4.2 shipped with the silent ABI break
- 2026-05-26 — Sven opens #89; Lior acknowledges, says "yank tomorrow morning CET"
- **2026-05-27 — v0.4.2 yanked from crates.io** (canonical date)
- 2026-05-28 — v0.4.3 ships with the revert
- 2026-06-01 — ABI assertion lands on the v0.5 branch (the date the release notes misremember as the yank)
- 2026-06-08 — v0.5.0 ships; #89 closed
Answer
## Dates by source | Source | Date given | Where | |---|---|---| | v0.5.0 release notes | **2026-06-01** | release-v0.5.0-2026-06-08.md:169 ("A note on v0.4.2") | | Issue #89 header | **2026-05-27** | issue-089-plugin-api-break.md:8 ("Affected versions") | | Issue #89 thread | **2026-05-27** | issue-089-plugin-api-break.md:159–163 — Lior posts the "Yanked. crates.io banner now reads…" comment dated 2026-05-27 | | May 2026 retro | **2026-05-27** | retro-may-2026.md:63 | A small correction to th…
Judge: covers all asked facts
SMFS Won View raw JSON
Input
169k
Output
293
Steps
7
Tools
3
Latency
30.1s
Cost
$2.56
#2 Reasoning 94 chars 
I'll search the agent memory for information about the v0.4.2 yank across those three sources.
#3 Edited agent_memory/profile.md 8,019 chars
Command Read 
{
  "file_path": "/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory/profile.md"
}
Result 9 lines 
1	# Memory Profile
2	# This file is auto-generated from your memories.
3	# It is not editable. To update, modify the source files
4	# that contain this information.
5	
6	## Core Knowledge
7	- Lior Brennan-Zhou was born in Toronto, Canada on 1988-03-15.
8	- Lior Brennan-Zhou identifies as he/him and uses the GitHub handle 'lior-bz'.
9	- Kavya Iyer is a software contributor based in Bangalore, India…
#4 Ran smfs grep "v0.4.2 yank" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory/ 5,366 chars
Command Bash 
smfs grep "v0.4.2 yank" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory/

{
  "description": "Search for v0.4.2 yank references in agent memory"
}
Result 7 lines 
# supermemory semantic search — 10 results for "v0.4.2 yank"
# searches by meaning across files in this container. usage:
#   grep "natural language query"          search all files
#   grep "query" path/to/dir/              search within directory
# output: <filepath>:<line_start>-<line_end>:<chunk> (chunk text is verbatim from the file)

/issues/issue-089-plugin-api-break.md:147-157:## @kitplug-…
#5 Ran smfs grep "v0.5.0 release" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory/ 4,908 chars
Command Bash 
smfs grep "v0.5.0 release" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory/

{
  "description": "Search for v0.5.0 release notes in agent memory"
}
Result 7 lines 
# supermemory semantic search — 10 results for "v0.5.0 release"
# searches by meaning across files in this container. usage:
#   grep "natural language query"          search all files
#   grep "query" path/to/dir/              search within directory
# output: <filepath>:<line_start>-<line_end>:<chunk> (chunk text is verbatim from the file)

/memory/profiles/lior-brennan-zhou.md:Lior Brennan-Zhou…
#7 Reasoning 1,395 chars 
Here's what each source says:

**Issue #89** — The comment timestamps tell a clear story:
- **2026-05-26**: Sven asks for a yank; Lior replies "Yank tomorrow morning CET."
- **2026-05-27**: Lior posts "Yanked. crates.io banner now reads: `kitabi 0.4.2 yanked: ABI break, see #89.`"

So issue #89 gives the yank date as **2026-05-27**.

**May 2026 retro** (`notes/retro-may-2026.md`) — States explicitly:
> "v0.4.2 was yanked from crates.io on **2026-05-27**."

This matches issue #89 exactly.

**v0.5.0 release notes** (`releases/release-v0.5.0-2026-06-08.md`) — States:
> "v0.4.2 was yanked from crates.io on **2026-06-01**."

This is 5 days later than the other two sources.

---

**Reconciliation:** The yank happened on **2026-05-27**. Issue #89 provides the strongest evidence — it has contemporaneous, timestamped comments where Lior announced the yank on that date, and the May retro (written at month's end, while the event was still fresh) corroborates it. The v0.5.0 release notes were written on 2026-06-08, eleven days after the fact, and the "June 1" date is almost certainly a simple misrecollection by Lior when drafting the release notes.

(Side note: the release notes also claim "There is no v0.4.3," but issue #89 has Sven confirming v0.4.3 shipped on 2026-05-28 — another sign that section of the release notes was written from memory rather than checked against the record.)
Answer
Here's what each source says: **Issue #89** — The comment timestamps tell a clear story: - **2026-05-26**: Sven asks for a yank; Lior replies "Yank tomorrow morning CET." - **2026-05-27**: Lior posts "Yanked. crates.io banner now reads: `kitabi 0.4.2 yanked: ABI break, see #89.`" So issue #89 gives the yank date as **2026-05-27**. **May 2026 retro** (`notes/retro-may-2026.md`) — States explicitly: > "v0.4.2 was yanked from crates.io on **2026-05-27**." This matches issue #89 exactly. **v0.5…
Judge: covers all asked facts