-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency zustand to v5 #449
Open
renovate
wants to merge
1
commit into
develop
Choose a base branch
from
renovate/zustand-5.x
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 15, 2024 04:34
69fb228
to
8c9a3bd
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 15, 2024 15:29
8c9a3bd
to
3b3e2a7
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 16, 2024 02:08
3b3e2a7
to
636c580
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 16, 2024 11:31
636c580
to
20c4274
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 16, 2024 21:48
20c4274
to
995cf94
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 17, 2024 01:44
995cf94
to
af3f305
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 17, 2024 09:38
af3f305
to
be6c81f
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 17, 2024 21:24
be6c81f
to
696a499
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 18, 2024 13:36
696a499
to
597379c
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 18, 2024 20:04
597379c
to
bff2d1b
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 19, 2024 07:55
bff2d1b
to
dc0dc15
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 19, 2024 17:00
dc0dc15
to
03f90d4
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 20, 2024 10:32
03f90d4
to
b580cf7
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 21, 2024 22:13
b580cf7
to
bd9011c
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 22, 2024 00:57
bd9011c
to
188b821
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 22, 2024 03:27
188b821
to
974abe9
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 22, 2024 22:45
974abe9
to
ee86e0a
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 23, 2024 08:28
ee86e0a
to
f919be9
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 23, 2024 15:40
f919be9
to
dde5572
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 24, 2024 01:11
dde5572
to
f1dbe4d
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 24, 2024 17:01
f1dbe4d
to
5866c88
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 24, 2024 22:24
5866c88
to
0859631
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 25, 2024 10:48
0859631
to
4751e89
Compare
renovate
bot
force-pushed
the
renovate/zustand-5.x
branch
from
October 27, 2024 09:30
4751e89
to
c6770a9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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 contains the following updates:
4.5.5
->5.0.0
Release Notes
pmndrs/zustand (zustand)
v5.0.0
Compare Source
🎉🎉🎉 Zustand v5 🐻🐻🐻
TL;DR
Migration Guide
Read the migration guide carefully:
https://github.com/pmndrs/zustand/blob/main/docs/migrations/migrating-to-v5.md
Frequently Reported Issue
During the RC period, some users encountered the following infinite loop error:
This case was already a non-ideal behavior in v4 but appears more explicitly as an error in v5. While there are several ways to resolve this, using
useShallow
often fixes the problem.What's Changed
setState
by @chrisvander in https://github.com/pmndrs/zustand/pull/2696New Contributors
Full Changelog: pmndrs/zustand@v4.5.5...v5.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.