Migration guide: point Paths 7 and 8 at the current 2026.6.4 baseline#21
Conversation
Paths 9/10/12 were updated in #20 but Paths 7 and 8 still referenced superseded endpoints (2026.5.22 / 2026.5.24-beta.1). Point them through Path 10 and Path 12. Co-Authored-By: Rob <onerobby@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| ## Path 7: v2026.4.27 stable → v2026.4.29-beta.1 | ||
|
|
||
| Former beta jump. If you're upgrading today, treat this as the conceptual migration step for memory/messaging behavior and then continue to 2026.5.22 stable. | ||
| Former beta jump. If you're upgrading today, treat this as the conceptual migration step for memory/messaging behavior, then continue through Path 10 and Path 12 to the current 2026.6.4 stable baseline. |
There was a problem hiding this comment.
🟡 Path 7 forward-reference skips required intermediate Path 8
Path 7 ends at v2026.4.29-beta.1, but the updated text tells readers to "continue through Path 10 and Path 12" — skipping Path 8 entirely. Path 10 (part26-migration-guide.md:256) accepts v2026.5.14-beta.1 / v2026.5.12 as input, not v2026.4.29-beta.1. Readers following this guidance literally would skip Path 8 (v2026.4.29-beta.1 → v2026.5.12 stable) and land on a Path 10 whose input version range doesn't include where they are. The old text ("continue to 2026.5.22 stable") was vague but version-correct; the new text is specific but omits a required step. Compare with Path 9 at line 233, which correctly says "continue through Path 10 and Path 12" because Path 9 ends at v2026.5.14-beta.1, which Path 10 does accept.
| Former beta jump. If you're upgrading today, treat this as the conceptual migration step for memory/messaging behavior, then continue through Path 10 and Path 12 to the current 2026.6.4 stable baseline. | |
| Former beta jump. If you're upgrading today, treat this as the conceptual migration step for memory/messaging behavior, then continue through Path 8, Path 10, and Path 12 to the current 2026.6.4 stable baseline. |
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Correct — Path 7 ends at 2026.4.29-beta.1 and Path 10 only accepts 5.12/5.14-beta.1, so it has to pass through Path 8 first. Fixed in 47131e6: now "continue through Path 8, Path 10, and Path 12."
Path 7 ends at 2026.4.29-beta.1; Path 10 accepts 5.12/5.14-beta.1, so the chain must pass through Path 8 (4.29-beta.1 -> 5.12) first. Co-Authored-By: Rob <onerobby@gmail.com>
1 participant
Summary
Follow-up to #20. That PR updated migration Paths 9, 10, and the new Path 12 to route upgraders to the current 2026.6.4 stable baseline, but Paths 7 and 8 still named superseded endpoints, leaving an inconsistent upgrade narrative (flagged by Devin Review on #20):
v2026.4.27 → v2026.4.29-beta.1) ended with "continue to 2026.5.22 stable".v2026.4.29-beta.1 → v2026.5.12 stable) ended with "continue to Path 10 before experimenting with 2026.5.24-beta.1" (since promoted to stable in 2026.5.26).Both now route through Path 10 and Path 12 to 2026.6.4, matching how Paths 9/10 already read.
Type of change
Review checklist
markdownlint-cli2andlychee --offlinelocally (0 errors, 0 broken links)Notes / flagged items
part26-migration-guide.md). No intermediate-step facts changed — only the "where to go next" endpoints.Link to Devin session: https://app.devin.ai/sessions/3b1d5b0b85964b2bb4b87bab0979ed3f
Requested by: @OnlyTerp