chore: sync develop_v4 with stage_v4 - #645
Merged
Merged
Conversation
develop to stage 6 aug release
Co-Authored-By: Claude <noreply@anthropic.com>
Release v4.5.0
DOMPurify before 3.4.13 has an XSS bypass where IN_PLACE sanitization combined with element-removal hooks can leave a detached DOM subtree with executable event handlers (GHSA-55q2-fjhq-7xh7). Bumps the dependency from ^3.4.12 to ^3.4.13, the first patched release. Co-Authored-By: Claude <noreply@anthropic.com>
Clears 9 advisories (8 high, 1 moderate) in postcss, vite, and ws. Lockfile only; no package.json ranges changed. Co-Authored-By: Claude <noreply@anthropic.com>
Spec fixtures used ad hoc api key strings that read like real stack keys (bltanything, bltapikey, livePreviewApiKey123, test-key), so sample data was hard to tell apart from meaningful values. Replace them all with YOUR_API_KEY. The one exception is the test asserting that a user-config api key takes precedence over an SDK header api key, where the header keeps a distinct YOUR_HEADER_API_KEY so the assertion still proves precedence rather than passing trivially. Co-Authored-By: Claude <noreply@anthropic.com>
…hook-removal fix(security): bump dompurify to patch XSS vulnerability
…lues-in-tests chore(tests): standardize api key placeholder values in specs
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
Coverage Report
File CoverageNo changed files found. |
Merged
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
4 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.
develop_v4 is behind stage_v4 by the 4.5.0 release commits and the security bump that followed, so anything branched off develop_v4 today starts without them. This branch is develop_v4 with stage_v4 merged into it.
What comes in:
npm audit fixthat went with it (fix(security): bump dompurify to patch XSS vulnerability #638)The merge was clean, no conflicts resolved by hand.
Replaces #644, which pointed stage_v4 straight at develop_v4 and could not be merged: develop_v4 requires the head branch to be up to date, and updating stage_v4 needs its own PR, so the two branches blocked each other. A branch that already carries both sides breaks that loop. Merging this first also unblocks #640, since develop_v4 will then contain stage_v4's tip.
🤖 Generated with Claude Code