Skip to content

docs: update migration guide to use @latest instead of pinned v0.8.18#468

Merged
bradygaster merged 1 commit intobradygaster:devfrom
tamirdresher:contrib/docs-migration-guide-latest-320
Mar 20, 2026
Merged

docs: update migration guide to use @latest instead of pinned v0.8.18#468
bradygaster merged 1 commit intobradygaster:devfrom
tamirdresher:contrib/docs-migration-guide-latest-320

Conversation

@tamirdresher
Copy link
Copy Markdown
Collaborator

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:

  • *Replaced all pinned @0.8.18* install commands with @latest\
  • Updated Quick Reference table from \�0.8.18\ → \�0.8.x (@latest)\
  • Updated Scenario 2 (v0.5.4 upgrade) to install latest
  • Updated Scenario 3 expected version output to be generic
  • Updated Scenario 8 (CI/CD) to use Node.js 20 and @latest, with note about pinning specific versions
  • Updated troubleshooting commands to use @latest\
  • Updated Rolling Back section to use current version examples
  • Expanded What's New section to include v0.8.23+ and v0.8.25+ improvements

What's Preserved

  • Blog posts (021, 022) are left untouched — they're historical records of the v0.8.18 launch
  • CHANGELOG.md references are historical
  • The section heading \What's New in v0.8.18+\ kept as it marks the landmark migration release

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.

@bradygaster bradygaster changed the base branch from main to dev March 20, 2026 03:54
@bradygaster bradygaster reopened this Mar 20, 2026
@bradygaster bradygaster reopened this Mar 20, 2026
@bradygaster bradygaster changed the base branch from dev to main March 20, 2026 04:21
@bradygaster bradygaster changed the base branch from main to dev March 20, 2026 04:21
…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>
@bradygaster bradygaster force-pushed the contrib/docs-migration-guide-latest-320 branch from 85b0094 to f2568b5 Compare March 20, 2026 08:23
@bradygaster bradygaster merged commit 61cb23a into bradygaster:dev Mar 20, 2026
2 checks passed
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>
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.

Docs: Migration guide pins v0.8.18 — should reference latest or @latest

2 participants