Skip to content

chore: bump dompurify from 3.4.16 to 3.4.17 (#13252) (CP: 25.3) - #13254

Merged
web-padawan merged 1 commit into
25.3from
cherry-pick-13252-to-25.3-1792774732948
Oct 23, 2026
Merged

web-padawan merged 1 commit into
25.3from
cherry-pick-13252-to-25.3-1792774732948

Conversation

@vaadin-bot

Copy link
Copy Markdown
Collaborator

This PR cherry-picks changes from the original PR #13252 to branch 25.3.

Warning

The cherry-pick had merge conflicts that were resolved automatically by Claude Code. Please review the changes carefully.

Resolution notes from Claude:

  • packages/markdown/package.json: kept 25.3 versions of @​vaadin/component-base and @​vaadin/vaadin-themable-mixin (~25.3.4), took dompurify ^3.4.17.
  • yarn.lock: replaced the 25.3 dompurify@​^3.4.10 (3.4.13) entry with the dompurify@​^3.4.17 (3.4.17) entry from the pick.
  • Conflict came from 25.3 still being on dompurify ^3.4.10; the earlier bump chore: bump dompurify from 3.4.13 to 3.4.16 #12972 (3.4.13 -> 3.4.16) is missing on 25.3, this pick jumps straight to 3.4.17.
  • Verified: yarn --frozen-lockfile, yarn lint:types, yarn test --group markdown (26 passed).

Bumps dompurify from 3.4.16 to 3.4.17.

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.17

  • Fixed an issue with IN_PLACE, SAFE_FOR_TEMPLATES and shadow roots, thanks @​manus-pi
  • Fixed IN_PLACE handling of nodes that hooks or custom elements tough during sanitization, thanks @​uttej-badwane
  • Fixed the SMIL attributeName guard in XHTML mode, thanks @​Koukyosyumei
  • Hardened several smaller edge cases (namespaces, literal-text elements, isValidAttribute()), thanks @​artiphishell
  • Added a purify-edge test runner as a compatibility check, thanks @​anzal1
  • Clarified the IN_PLACE documentation in the README about possible risks
  • Updated several dependencies
Commits

Dependabot compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Resolution notes:
- packages/markdown/package.json: kept 25.3 versions of @vaadin/component-base and @vaadin/vaadin-themable-mixin (~25.3.4), took dompurify ^3.4.17.
- yarn.lock: replaced the 25.3 dompurify@^3.4.10 (3.4.13) entry with the dompurify@^3.4.17 (3.4.17) entry from the pick.
- Conflict came from 25.3 still being on dompurify ^3.4.10; the earlier bump #12972 (3.4.13 -> 3.4.16) is missing on 25.3, this pick jumps straight to 3.4.17.
- Verified: yarn --frozen-lockfile, yarn lint:types, yarn test --group markdown (26 passed).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@web-padawan
web-padawan merged commit 2212652 into 25.3 Oct 23, 2026
12 checks passed
@web-padawan
web-padawan deleted the cherry-pick-13252-to-25.3-1792774732948 branch October 23, 2026 17:10
@vaadin-bot

Copy link
Copy Markdown
Collaborator Author

This ticket/PR has been released with Vaadin 25.3.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants