Skip to content

docs(migration): anchor v3→v4 adopter numbers to v4.0 release, point to live codemod#522

Merged
bokelley merged 3 commits intomainfrom
claude/issue-520-migration-guide-numbers
May 4, 2026
Merged

docs(migration): anchor v3→v4 adopter numbers to v4.0 release, point to live codemod#522
bokelley merged 3 commits intomainfrom
claude/issue-520-migration-guide-numbers

Conversation

@bokelley
Copy link
Copy Markdown
Contributor

@bokelley bokelley commented May 4, 2026

Closes #520

The MIGRATION_v3_to_v4.md guide cited "270 files scanned, 161 test-collection failures" as if these were current migration difficulty benchmarks. They are real adopter data, but from the v4.0 release period — before subsequent alias coverage and codemod improvements that materially reduced finding counts at v4.3+. The misleading framing caused an adopter to expect worse migration pain than they actually hit.

This PR anchors the data point temporally ("at v4.0 release"), adds a standalone disclaimer sentence clarifying the figures reflect initial-release tooling, and redirects adopters to run the codemod against their own tree for a current count — so the note ages gracefully without becoming another stale number.

The cascade mechanics explanation (import re-export amplification, ordering steps) is unchanged; those are version-independent.

What was tested

  • Verified markdown renders correctly (prose-only change, no code touched)
  • ruff check . — not applicable (no Python files changed)
  • mypy src/ — not applicable (no Python files changed)

Pre-PR review

  • code-reviewer: approved — no blockers; nit on sentence seam (noted below), changeset correctly omitted for release-please repo
  • docs-expert: approved — blocker from round 1 (nested em-dash + semicolon in parenthetical) resolved by restructure; one nit applied ("before subsequent alias coverage…")

Noted nits not fixed (pre-existing): the salesagent re-exported through… line is technically a sentence fragment; the two-idea paragraph could use a blank-line break between the data point and the cascade narrative. Neither was introduced by this PR.

Triage-managed PR. This bot does not currently iterate on
review comments or PR conversation threads (only on the source
issue). To unblock:

  • Push fixup commits directly: gh pr checkout <num>
    fix → push.
  • Or re-trigger: comment /triage execute on the source
    issue.

See adcp#3121
for context.

Session: https://claude.ai/code/session_0138z8359JAkARZJWfmBLprE


Generated by Claude Code

claude added 3 commits May 4, 2026 01:07
…to live codemod

The "270 files / 161 test-collection failures" paragraph read as a current
migration-difficulty forecast; it is actually a v4.0-era worst-case baseline.
v4.3+ alias coverage and codemod improvements have materially reduced finding
counts. Adds temporal context and redirects adopters to run the codemod against
their own tree for a current estimate, so the note ages gracefully without
becoming a second stale number.

Closes #520

https://claude.ai/code/session_0138z8359JAkARZJWfmBLprE
Pull figures outside the parenthetical and make the disclaimer a standalone
sentence — resolves pre-PR review finding that em-dash + semicolon nested
inside a parenthetical was hard to parse (human and agent readers both).
No meaning change; intent and all data points preserved.

https://claude.ai/code/session_0138z8359JAkARZJWfmBLprE
…k note

Nit from pre-PR review: 'before alias coverage and codemod improvements'
was vague about timing. 'Before subsequent' makes the temporal arc explicit.

https://claude.ai/code/session_0138z8359JAkARZJWfmBLprE
@bokelley bokelley marked this pull request as ready for review May 4, 2026 02:00
@bokelley bokelley merged commit 11732c8 into main May 4, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: refresh migration guide 'what to expect' numbers against current snapshot

2 participants