Repository navigation
feat: add scoped stores and prepare 2.0.0 release - #11
Merged
Merged
Conversation
ljlm0402
changed the title
ljlm0402
marked this pull request as ready for review
October 18, 2026 09:04
ljlm0402
changed the title
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
Add createStoreContext for typed component-tree and SSR-request scoped stores, update the Counter example, and prepare the 2.0.0 stable release. The combined release includes persistence migration/recovery and error-handling contract changes from merged #10; migration guidance explains the breaking changes.
Set package.json and npm lockfile versions to 2.0.0. Validate source/lockfile/tarball versions and Git tag equality; stable releases use latest and prereleases use next. Both CLI channel paths are tested. PR and publish workflows also check a packed consumer with minimum supported Vue 3.2.0.
Keep both READMEs at the root and move the review report, release notes, release plan and roadmap to docs/. Update README links and the release plan for stable preparation. Preserve the GitHub PR template in its functional .github location.
Validation
Release status and limits
2.0.0 is prepared, not published. No release tag has been created; review/merge and publication remain separate. No RC publication or real consumer application validation is claimed. Factories must synchronously return fresh stores; SSR apps must be request-local. Automatic hydration/serialization, selector subscriptions and asynchronous storage are outside this release. The release plan records application verification and data rollback requirements.