Skip to content

Bump the npm_and_yarn group across 1 directory with 2 updates#553

Open
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/docusaurus/npm_and_yarn-8ef8040ea6
Open

Bump the npm_and_yarn group across 1 directory with 2 updates#553
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/docusaurus/npm_and_yarn-8ef8040ea6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 17, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm_and_yarn group with 2 updates in the /docusaurus directory: dompurify and ws.

Updates dompurify from 3.4.1 to 3.4.10

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.10

  • Refactored codebase for clarity: extracted the public type declarations into types.ts
  • Decomposed the three largest sanitizer functions into focused helpers
  • Removed duplicated defaults and dead branches, consolidated SAFE_FOR_TEMPLATES scrubbing into single shared path
  • Improved per-node performance by hoisting the mXSS probe regexes and testing textContent before innerHTML
  • Added a deterministic micro-benchmark harness (npm run bench) with a --compare mode
  • Reduced CI cost by running the full three-engine browser suite once per PR
  • Refreshed the demos/ folder so every demo runs again, and added a SVG-via-<img> demo
  • Documented the bench and test:happydom scripts in the README
  • Completed the Attack Classes & Bypass History wiki page
  • Bumped several dependencies where possible

DOMPurify 3.4.9

  • Further improved the handling of Trusted Types config options, thanks @​offset
  • Further improved the handling of IN_PLACE sanitization, thanks @​mozfreddyb
  • Added more test coverage for IN_PLACE and Trusted Types related usage
  • Bumped several dependencies where possible
  • Updated README and wiki with more accurate documentation & attack samples

DOMPurify 3.4.8

  • Cleaned up the repository root, renamed some and removed unneeded files
  • Fixed an issue with handling of Trusted Types policies, thanks @​fulstadev
  • Fixed the node iterator for better template scrubbing, thanks @​IamLeandrooooo
  • Included formerly missing LICENSE-MPL in published npm package, thanks @​asamuzaK
  • Bumped several dependencies where possible

DOMPurify 3.4.7

  • Hardened the handling of Shadow Roots when using IN_PLACE, thanks @​GameZoneHacker
  • Removed a problem leading to permanent hook pollution, thanks @​offset
  • Refactored the test suite and expanded test coverage significantly

DOMPurify 3.4.6

  • Fixed several issues with DOM Clobbering in IN_PLACE mode, thanks @​offset & @​Bankde
  • Hardened the checks for cross-realm IN_PLACE and Shadow DOM sanitization, thanks @​offset & @​Bankde
  • Added more test coverage for IN_PLACE and general DOM Clobbering attacks
  • Bumped several dependencies where possible

DOMPurify 3.4.5

  • Fixed a bypass caused by the new HTML element selectedcontent added in 3.4.4, thanks @​KabirAcharya

Note that this is a security release for an issue introduced in 3.4.4 and should be upgraded to immediately.

DOMPurify 3.4.4

  • Added the selectedcontent element to default allow-list, thanks @​lukewarlow
  • Added the command and commandfor attributes to default allowed-list, thanks @​lukewarlow
  • Added better template scrubbing for IN_PLACE operations, thanks @​DEMON1A
  • Added stronger checks for cross-realm windows, thanks @​DEMON1A & @​fg0x0
  • Updated demo website and made sure it uses the latest from main
  • Updated existing workflows, fuzzer, dependabot, etc., added more tests
  • Bumped several dependencies where possible

... (truncated)

Commits

Updates ws from 7.5.10 to 7.5.11

Release notes

Sourced from ws's releases.

7.5.11

Bug fixes

  • Backported 2b2abd45 to the 7.x release line (e14c4586).
Commits

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump the npm_and_yarn group across 1 directory with 2 updates
a73e7cd 
Bumps the npm_and_yarn group with 2 updates in the /docusaurus directory: [dompurify](https://github.com/cure53/DOMPurify) and [ws](https://github.com/websockets/ws).


Updates `dompurify` from 3.4.1 to 3.4.10
- [Release notes](https://github.com/cure53/DOMPurify/releases)
- [Commits](cure53/DOMPurify@3.4.1...3.4.10)

Updates `ws` from 7.5.10 to 7.5.11
- [Release notes](https://github.com/websockets/ws/releases)
- [Commits](websockets/ws@7.5.10...7.5.11)

---
updated-dependencies:
- dependency-name: dompurify
  dependency-version: 3.4.10
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: ws
  dependency-version: 7.5.11
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 17, 2026
@mergify mergify Bot added documentation Improvements or additions to documentation size/xs labels Jun 17, 2026
@mergify

mergify Bot commented Jun 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 5 minutes 59 seconds in the queue, including 4 seconds running CI.

Waiting for
  • #approved-reviews-by>=1
  • check-success=PR Status Check
  • any of: [🛡 GitHub branch protection]
    • check-neutral = PR Status Check
    • check-skipped = PR Status Check
    • check-success = PR Status Check
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = PR Status Check
    • check-skipped = PR Status Check
    • check-success = PR Status Check
All conditions

Reason

Pull request #553 has been dequeued

merge conditions no longer match. Blocked by:

  • #approved-reviews-by>=1

  • #approved-reviews-by>=1

  • check-success=PR Status Check

  • any of [🛡 GitHub branch protection]:

    • check-neutral = PR Status Check
    • check-skipped = PR Status Check
    • check-success = PR Status Check

  • any of [🛡 GitHub repository ruleset rule main]:

    • check-neutral = PR Status Check
    • check-skipped = PR Status Check
    • check-success = PR Status Check

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@mergify mergify Bot added the queued label Jun 17, 2026
mergify Bot added a commit that referenced this pull request Jun 17, 2026
@mergify
Merge of #553
ef1332c
@mergify mergify Bot mentioned this pull request Jun 17, 2026
Closed
26 tasks
@mergify mergify Bot added dequeued and removed queued labels Jun 17, 2026
@mergify mergify Bot removed the dequeued label Jun 29, 2026
@mergify

mergify Bot commented Jun 29, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 6 minutes in the queue, including 7 seconds running CI.

Waiting for
  • #approved-reviews-by>=1
  • check-success=PR Status Check
  • any of: [🛡 GitHub branch protection]
    • check-neutral = PR Status Check
    • check-skipped = PR Status Check
    • check-success = PR Status Check
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @github-actions/PR Status Check
    • check-skipped = @github-actions/PR Status Check
    • check-success = @github-actions/PR Status Check
All conditions

Reason

Pull request #553 has been dequeued

merge conditions no longer match. Blocked by:

  • #approved-reviews-by>=1

  • #approved-reviews-by>=1

  • check-success=PR Status Check

  • any of [🛡 GitHub branch protection]:

    • check-neutral = PR Status Check
    • check-skipped = PR Status Check
    • check-success = PR Status Check

  • any of [🛡 GitHub repository ruleset rule main]:

    • check-neutral = @github-actions/PR Status Check
    • check-skipped = @github-actions/PR Status Check
    • check-success = @github-actions/PR Status Check

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

  • Requeue this pull request

@mergify mergify Bot added the queued label Jun 29, 2026
mergify Bot added a commit that referenced this pull request Jun 29, 2026
@mergify
Merge of #553
d31d514
This was referenced Jun 29, 2026
Open
Closed
@mergify mergify Bot added dequeued and removed queued labels Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file dequeued documentation Improvements or additions to documentation javascript Pull requests that update javascript code size/xs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants