Bump the npm-security-updates group across 1 directory with 2 updates - #3815

Sourced from colord's releases.

v2.10 (RGB color mixing)

• mix, tints, shades and tones (mix plugin) now accept an optional interpolation color space. LAB stays the default; pass "rgb" to interpolate RGB channels instead — the way browsers and design tools (such as Figma) composite translucent layers.

import { colord, extend } from "colord";
import mixPlugin from "colord/plugins/mix";
extend([mixPlugin]);
colord("#ff0000").mix("#ffffff", 0.5, "rgb").toHex(); // "#ff8080"
colord("#f0f3f1").mix("#007d40", 0.14, "rgb").toHex(); // "#cee2d8" — same as compositing rgba(0, 125, 64, 0.14) over #f0f3f1
colord("#ff0000").tints(3, "rgb").map((c) => c.toHex()); // ["#ff0000", "#ff8080", "#ffffff"]

Sourced from colord's changelog.

2.10.0

• Improve mix plugin by adding an optional "rgb" interpolation mode to mix, tints, tones and shades

2.9.7

• Make HEX parsing and serialization more than 2x faster

2.9.6

• Fix: Rotate the unrounded hue so rotate and harmonies preserve the original color
• Fix: Normalize HWB whiteness + blackness over 100% to gray ❤️ @​spokodev

2.9.5

• Fix: Use adjusted chroma for the CIEDE2000 rotation term ❤️ @​maximilliangrand
• Fix: Keep the hue within [0, 360) in every color model ❤️ @​sarathfrancis90

Both fixes change returned numbers for a small set of colors; toHex() output is unchanged. Snapshots holding h: 360, "hsl(360, …)" or a delta() value may need updating.

2.9.4

• Fix: Reject malformed color strings in linear time ❤️ @​GAP-dev

• See full diff in compare view

Sourced from svgo's releases.

v3.3.5

What's Changed

Security

• Backport the removeScriptElement hardening from SVGO v4 in #2269:
  • reject executable data: URLs and legacy vbscript: URLs
  • sanitize executable HTML inside <foreignObject> elements
  • handle namespace-prefixed SVG anchors and URL schemes containing ASCII tabs or newlines

This addresses GHSA-4vpr-x523-8j87 and GHSA-w27v-7q3p-w38r for the v3 release line.

Support

SVGO v3 is not officially supported; please consider upgrading to SVGO v4. This security fix has been backported, but there is no commitment to backport more complex changes in the future.

See the migration guide from v3 to v4.

• 4380590 ci: configure v3 publish tag in package metadata (#2271)
• 4c84fe7 ci: publish v3 with npm trusted publishing (#2270)
• 994a9f0 fix(removeScriptElement): backport security hardening to v3 (#2269)
• See full diff in compare view

This version was pushed to npm by GitHub Actions, a new releaser for svgo since your current version.

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.