chore(deps): bump dompurify from 3.4.12 to 3.4.13 - #153
Conversation
Bumps [dompurify](https://github.com/cure53/DOMPurify) from 3.4.12 to 3.4.13. - [Release notes](https://github.com/cure53/DOMPurify/releases) - [Commits](cure53/DOMPurify@3.4.12...3.4.13) --- updated-dependencies: - dependency-name: dompurify dependency-version: 3.4.13 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
![mif-automerge[bot]](https://avatars.githubusercontent.com/in/4187029?s=60&v=4){kind=small}
…ile bumps (#156) sca / osv-scanner has failed on main and every PR since the advisories published, which also blocks the automerge of catalog re-pin PRs (#155 sat BLOCKED on it). Bump each package within its existing semver range: dompurify 3.4.12 -> 3.4.13 (GHSA-55q2-fjhq-7xh7), js-yaml 4.3.0 -> 4.3.1 (GHSA-5p4m-2wfm-xmqj), nanoid 3.3.16 -> 3.3.18 (GHSA-2v37-7h3g-55p8), mermaid 11.16.0 -> 11.16.1 (5 advisories). Lockfile-only, no manifest changes; astro build passes. Supersedes Dependabot #153/#154.
|
Superseded by #156, which bumped dompurify to 3.4.13 (along with js-yaml, nanoid, and mermaid) in one lockfile-only pass to clear the failing osv-scanner gate; dompurify is already 3.4.13 on main. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
1 participant
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps dompurify from 3.4.12 to 3.4.13.
Release notes
Sourced from dompurify's releases.
Commits
3067f77release: 3.4.13 (#1562)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.