Repository navigation
Enter beta: XState v6 pre-release moves from alpha to beta - #5762
davidkpiano wants to merge 7 commits into
Conversation
🦋 Changeset detectedLatest commit: d41e29b The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
6b0a345 to
f08f2f8
Compare
|
Resolved the conflict against current The conflicting Validation:
|
# Conflicts: # packages/core/package.json # packages/xstate-effect/package.json # packages/xstate-test/package.json
f08f2f8 to
b4d82b6
Compare
# Conflicts: # packages/core/package.json # packages/xstate-codemod/package.json # packages/xstate-effect/package.json # packages/xstate-react/package.json # packages/xstate-scxml/package.json # packages/xstate-test/package.json
# Conflicts: # packages/core/package.json
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| { | ||
| "mode": "pre", | ||
| "tag": "alpha" | ||
| "tag": "beta" |
There was a problem hiding this comment.
🟡 Installation guides still select alpha releases
After tag moves to beta, the quick-start guide still installs xstate@alpha. Readers following it receive an older prerelease instead of the beta described here.
Learn more
The prerelease tag selects which version npm install xstate@<tag> fetches. The quick-start guide, framework guide, migration guide, and affected package guides still instruct readers to install alpha. After the beta release, these commands fetch the previous alpha rather than the new beta, leaving new users on older APIs. The repository's documentation rule requires auditing these guides alongside a behavior change.
Example: A reader copies npm install xstate@alpha from the quick start after 6.0.0-beta.0 publishes. npm selects the last alpha, not 6.0.0-beta.0.
Recommended fix: Update install instructions and current-release descriptions for core, adapters, and Effect to @beta; retain @alpha only where it explicitly documents historical releases. Keep store instructions on @alpha, since those packages are excluded from this beta.
Was this helpful? React with 👍 or 👎 to provide feedback.
Moves the v6 pre-release from
alphatobeta..changeset/pre.json:tag: "beta"..changeset/config.json:@xstate/storeand@xstate/store-*are ignored; store does not ride the beta and ships 5.0 with XState 6.0 stable.X.Y.Z-betaso the prerelease counter starts atbeta.0..changeset/enter-beta.md: beta notice. No further breaking changes are planned for@publicAPIs; any that are needed will come with a migration path.@experimentalAPIs may still change.Dry run (
pnpm changeset status --verboseon this branch, rebased onnextafter #5814):xstate@xstate/react@xstate/vue@xstate/svelte@xstate/solid@xstate/test@xstate/effect@xstate/scxml@xstate/codemodStore packages are unchanged. No changeset mixes store and non-store packages.
Merge with #5806 (docs use
@betainstalls). After the "Version Packages (beta)" release, point thebetadist-tag at@xstate/effect,@xstate/codemodand@xstate/scxml(packages without a stable release publish prereleases tolatest).Verified:
pnpm install --frozen-lockfile,pnpm changeset status --verbose,pnpm build && pnpm check:packed.