docs: update migration guide to use @latest instead of pinned v0.8.18#468
Merged
bradygaster merged 1 commit intobradygaster:devfrom Mar 20, 2026
Conversation
…bradygaster#320) - Replace all pinned @0.8.18 install commands with @latest - Update version expectations to reference current 0.8.x line - Update CI/CD examples to use Node.js 20 and @latest - Add v0.8.23+ and v0.8.25+ improvements to What's New section - Keep v0.8.18 only in historical section heading (landmark release) Users following the migration guide were installing v0.8.18 which crashes on Node 22+ due to ESM import issues fixed in v0.8.23. Fixes bradygaster#320 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
85b0094 to
f2568b5
Compare
chrislomonico
pushed a commit
to clomonico/squad
that referenced
this pull request
Mar 26, 2026
…ygaster#468) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #320 — The migration guide hard-coded @0.8.18\ in all install commands, leading users to install a version that crashes on Node 22+ (ESM import issue fixed in v0.8.23).
Changes
\docs/src/content/docs/get-started/migration.md:
What's Preserved
Impact
Users following the migration guide will now install the current version instead of the 7-releases-old v0.8.18 that breaks on modern Node.js.