Bump dompurify from 3.3.3 to 3.4.1 - #11
Conversation
Bumps [dompurify](https://github.com/cure53/DOMPurify) from 3.3.3 to 3.4.1. - [Release notes](https://github.com/cure53/DOMPurify/releases) - [Commits](cure53/DOMPurify@3.3.3...3.4.1) --- updated-dependencies: - dependency-name: dompurify dependency-version: 3.4.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: afe5ca1d08
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| '@preact/signals-core@1.14.0': | ||
| resolution: {integrity: sha512-AowtCcCU/33lFlh1zRFf/u+12rfrhtNakj7UpaGEsmMwUKpKWMVvcktOGcwBBNiB4lWrZWc01LhiyyzVklJyaQ==} | ||
| '@preact/signals-core@1.14.1': |
There was a problem hiding this comment.
Bump dompurify in lockfile to the intended version
This change does not actually upgrade dompurify even though the commit is for a 3.3.3 -> 3.4.1 bump; the only version change here is @preact/signals-core to 1.14.1. In the resulting lockfile, dompurify still resolves to 3.3.3 (e.g. package and snapshot entries remain unchanged), so the DOMPurify 3.4.x fixes are not applied and the dependency update goal is not met.
Useful? React with 👍 / 👎.
Bumps dompurify from 3.3.3 to 3.4.1.
Release notes
Sourced from dompurify's releases.
Commits
5b0cdbbchore: merge main into 3.x for 3.4.1 release (#1301)09f5911test: added three more browsers to test setup (OSX, mobile)5b16e0bGetting 3.x branch ready for 3.4.0 release (#1250)Install script changes
This version adds
preparescript that runs during installation. Review the package contents before updating.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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.