Repository navigation
chore: release - #43
Merged
Merged
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@codebelt/classy-store@0.10.0
Minor Changes
#42
68bb261Thanks @codeBelt! - Bound optional framework peers to supported stable majors: React^18.0.0 || ^19.0.0, Vue^3.2.0, and Svelte^4.0.0 || ^5.0.0. Future majors are no longer accepted automatically. Development dependency versions remain unchanged.Fix the Vue adapter's public declaration to return
Ref<Snapshot<T>>backed by a shallow ref. Vue 3.2.0 does not export the newerShallowReftype; the stable type preserves readonly snapshot inference at the advertised minimum without changing runtime behavior.Validate packed consumers at React 18.0.0/19.0.0, Vue 3.2.0, and Svelte 4.0.0/5.0.0 using existing focused tests. Add the minimums to CI coverage and document Svelte 4's native deferred
$:computations versus Svelte 5's immediate$derivedreads. Store snapshots still update synchronously in the adapters, and ordinary core subscriptions remain batched.#42
68bb261Thanks @codeBelt! - Support all stable Angular 22 releases with the optional@angular/corepeer set to^22.0.0and updateinjectStoresignals synchronously while preserving Angular's native rendering schedule and ordinary core subscription batching. Ignore notifications during teardown and release each subscription with its Angular lifecycle.This removes support for Angular 21 and earlier. Use aligned Angular runtime/compiler packages from a stable Angular 22 release and a compatible TypeScript 6.0 toolchain. Development dependencies and the example remain pinned to 22.2.3. The
/angularimport path andinjectStore(store)signature are unchanged; imperative signal and computed reads now reflect writes immediately.Add zoneless input, computed, keyed-list, and cleanup regressions, an updated Angular example, and migration documentation. Validate packed consumers with aligned Angular 22.0.0 and 22.2.3 packages and run the shared focused browser tests for both versions in CI.