Skip to content

docs(release): 0.4.5 follow-ups — pdf_backends CHANGELOG entry + stale coding count#82

Merged
dongwhee merged 1 commit into
developfrom
docs/release-0.4.5-followups
Jun 7, 2026
Merged

docs(release): 0.4.5 follow-ups — pdf_backends CHANGELOG entry + stale coding count#82
dongwhee merged 1 commit into
developfrom
docs/release-0.4.5-followups

Conversation

@dongwhee

@dongwhee dongwhee commented Jun 7, 2026

Copy link
Copy Markdown
Collaborator

Two doc-only follow-ups from the post-release CHANGELOG tick-off (every src-touching commit v0.4.4..v0.4.5 mapped to an entry or deliberate omit):

  1. f4827c8 was under-described — it ships src/trawl/fetchers/pdf_backends.py and pdf.py routes through it at runtime (default pymupdf unchanged, heavy parsers behind lazy imports). Added a proper [0.4.5] Added entry; the keep-PyMuPDF research conclusion stays in Tests/research.
  2. CLAUDE.md self-contradiction — the 2026-04-22 longform bullet still said coding 23/24 next to the new Current status saying 24/24. Annotated as point-in-time (the arxiv_pdf_lora flake has since recovered).

No code change; no gates needed beyond review.

…e coding count

Post-tag tick-off of `git log v0.4.4..v0.4.5 --no-merges -- src/`
against CHANGELOG [0.4.5] found one src-shipping commit framed only
as research: f4827c8 ships src/trawl/fetchers/pdf_backends.py and
routes pdf.py through it at runtime (default pymupdf unchanged, heavy
parsers lazy). Add an Added entry; the keep-PyMuPDF research note
stays.

CLAUDE.md: the 2026-04-22 longform bullet still said coding 23/24,
contradicting the new Current status (24/24). Annotate it as a
point-in-time measurement whose arxiv_pdf_lora flake has since
recovered.
@dongwhee dongwhee merged commit 9f905e3 into develop Jun 7, 2026
4 checks passed
@dongwhee dongwhee deleted the docs/release-0.4.5-followups branch June 7, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant