Docs: Fix incorrect @next version specifiers

[kylegach]

What I did

Replace @next version specifiers with @latest in docs snippets and code examples.

(Note that this PR targets main, to only affect the latest docs.)

Checklist for Contributors

Testing

Manual testing

N/A

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

Greptile Summary

This pull request updates Storybook documentation to replace @next version specifiers with @latest across multiple documentation files and code snippets. The changes affect three key files:

1. docs/get-started/frameworks/angular.mdx - Updates the automigrate command example to use @latest instead of @next
2. docs/_snippets/init-command.md - Changes initialization commands for all package managers (npm, pnpm, yarn) to use @latest
3. docs/_snippets/storybook-upgrade.md - Updates upgrade commands across all package managers to use @latest

The change ensures that documentation examples direct users to the stable latest version of Storybook rather than pre-release versions. This is important because @next typically refers to pre-release or beta versions that may be unstable, while @latest refers to the most recent stable release. Since this PR targets the main branch (which affects the production documentation), it makes sense to standardize on @latest to provide users with stable, production-ready versions by default.

These snippet files are likely included in multiple documentation pages throughout the Storybook docs, so this change will have a broad impact on user-facing installation and upgrade instructions. The change aligns with standard package management practices and ensures consistency across all package manager examples.

Confidence score: 5/5

• This PR is extremely safe to merge with minimal risk
• Score reflects simple documentation changes with no code logic modifications
• No files require special attention as these are straightforward text replacements

[greptile-apps]

_{3 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 462d8ba

Command	Status	Duration	Result
nx run-many -t build --parallel=3	✅ Succeeded	1m 10s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-08-06 19:36:10 UTC