Next release - #3661
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
March 25, 2023 09:57
b2ef104 to
4c5b79e
Compare
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
1 participant
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 the packages will be published to npm 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
mobx-react@8.0.0
Major Changes
44a2cf42#3590 Thanks @urugator! - Functional components now useuseSyncExternalStore, which should prevent tearing - you have to update mobx, otherwise it should behave as previously.Improved displayName/name handling of functional components as discussed in DisplayName not being forwarded when wrapped in #3438.
Reactions of uncommited class components are now correctly disposed, fixes An exception is thrown when using Mobx6 and react18 in development mode #3492.
Reactions don't notify uncommited class components, avoiding the warning, fixes An exception is thrown when using Mobx6 and react18 in development mode #3492.
Removed symbol "polyfill" and replaced with actual Symbols.
Removed
this.renderreplacement detection + warning.this.renderis no longer configurable/writable (possibly BC).Class component instance is no longer exposed as
component[$mobx]["reactcomponent"](possibly BC).Deprecated
disposeOnUnmount, it's not compatible with remounting.Patch Changes
44a2cf42]:mobx-react-lite@4.0.0
Major Changes
44a2cf42#3590 Thanks @urugator! - Components now useuseSyncExternalStore, which should prevent tearing - you have to update mobx, otherwise it should behave as previously.Improved displayName/name handling as discussed in DisplayName not being forwarded when wrapped in #3438.
mobx@6.9.0
Minor Changes
44a2cf42#3590 Thanks @urugator! - Better support for React 18: Mobx now keeps track of a global state version, which updates with each mutation.