Repository navigation
Python: Build(deps): bump zustand in /python/packages/devui/frontend - #9833
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [zustand](https://github.com/pmndrs/zustand) in `/python/packages/devui/frontend` from 5.0.15 to 5.0.16. Updates `zustand` from 5.0.15 to 5.0.16 - [Release notes](https://github.com/pmndrs/zustand/releases) - [Commits](pmndrs/zustand@v5.0.15...v5.0.16) --- updated-dependencies: - dependency-name: zustand dependency-version: 5.0.16 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
requested review from
SergeyMenshykh,
Eduard van Valkenburg (eavanvalkenburg) and
Roger Barreto (rogerbarreto)
as code owners
October 29, 2026 14:36
dependabot
Bot
requested review from
Darren Cohen (dargilco),
Jose Alvarez (jpalvarezl),
sophia-ramsey and
westey (westey-m)
as code owners
October 29, 2026 14:36
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the Zustand dependency and lockfile update.
No open issues 🎉
1 file not reviewed
python/packages/devui/frontend/package-lock.json: Generated file
What changed in this PR
Updates Zustand from 5.0.15 to 5.0.16 in the Agent Framework DevUI frontend, bringing upstream state-management fixes and a React performance improvement.
Changes:
- Raises the Zustand dependency range to
^5.0.16. - Updates npm and Yarn lockfiles with the new version and integrity hashes; the npm lockfile also removes several
peermetadata flags.
| File | Description |
|---|---|
python/packages/devui/frontend/yarn.lock |
Locks Zustand to 5.0.16 for Yarn installs. |
python/packages/devui/frontend/package.json |
Updates the declared Zustand dependency range. |
python/packages/devui/frontend/package-lock.json |
Locks Zustand to 5.0.16 for npm installs and refreshes metadata. |
Review effort: Balanced
This branch was successfully deployed
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.
Bumps zustand in
/python/packages/devui/frontendfrom 5.0.15 to 5.0.16.Updates
zustandfrom 5.0.15 to 5.0.16Release notes
Sourced from zustand's releases.
Commits
382d29cv5.0.16b488323chore(deps): update dev dependencies (#3593)da2706cfix(persist): preserve external devtools action arguments (#3592)a1fea2efix(devtools): preserve shared connections during store cleanup (#3580)d867e6ffix(devtools): apply serialize.reviver when parsing devtools messages (#3568)dac22e1perf(react): don't memoize getServerSnapshot in useStore (#3563)d7a5583Clarify maintainer-guided contribution workflow (#3587)b57db4fdocs(create): document that state cannot be read during initialization (#3569)f094eebci: build the docs with pmndrs/docs@v4 (#3570)ea612a5docs: fix broken migrating-to-v5 link in README (#3567)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions