Repository navigation
Conversation
Member
Author
|
Superseded by #514, which merged the same dompurify 3.4.17 pin in the Studio frontend at 02:24 UTC. Closing this duplicate. The branch is kept. |
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.
Summary
mainsince the Monaco upgrade (alerts fix: bound auto-reconnect attempts to the step timeout (part of PT-25) #179 to chore(deps): bump golang.org/x/term from 0.44.0 to 0.45.0 #183, one critical).overridesentry instudio/frontend/package.jsonpins dompurify to 3.4.17. The lockfile resolves 3.4.17 everywhere.Test plan
npm ci(strict lockfile check)npm run build,typecheck:device-view,test:device-view(116),test:probescript(11),check:probescriptnpm audit --omit=devreports 0 vulnerabilities🤖 Generated with Claude Code