updated Svelte kit and adapter-node libraries and specified explicit dependency on devalue #33
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
…dependency on devalue
tomwheeler
requested review from
Alex-Tideman,
cretz,
paulnpdev and
robholland
as code owners
Alex-Tideman
approved these changes
Aug 29, 2025
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.
What was changed
I updated Svelte kit and adapter-node libraries and specified explicit dependency on devalue
Why?
This should hopefully address a high-severity dependabot alert opened a few hours ago.
Checklist
https://github.com/temporalio/reference-app-orders-web/security/dependabot/20
After making the changes, I ran
pnpm into && pnpm devand then processed an order to completion. I then looked atnode_modules/devalue/package.jsonand verified that the devalue library was version 5.3.2, which dependabot specifies contains the fix.No