chore(deps-dev): bump ip-address from 10.2.0 to 10.5.0

[dependabot]

Bumps ip-address from 10.2.0 to 10.5.0.

Release notes

Sourced from ip-address's releases.

v10.5.0

What's Changed

• Honor the fromURL graceful-failure contract for non-IPv6 hosts by @​beaugunderson in beaugunderson/ip-address#218
• Correct the documentation where it disagreed with the library by @​beaugunderson in beaugunderson/ip-address#219

Full Changelog: beaugunderson/ip-address@v10.4.0...v10.5.0

v10.4.0

What's Changed

• Add GitHub Actions CI by @​beaugunderson in beaugunderson/ip-address#213
• Keep the package loadable on node 12, and enforce it by @​beaugunderson in beaugunderson/ip-address#216
• Validate the byte arrays Address6 is given by @​beaugunderson in beaugunderson/ip-address#217

Full Changelog: beaugunderson/ip-address@v10.3.1...v10.4.0

v10.3.1

Full Changelog: beaugunderson/ip-address@v10.3.0...v10.3.1

v10.3.0

Full Changelog: beaugunderson/ip-address@v10.2.2...v10.3.0

v10.2.2

Full Changelog: beaugunderson/ip-address@v10.2.1...v10.2.2

v10.2.1

Full Changelog: beaugunderson/ip-address@v10.2.0...v10.2.1

Commits

• ef98e0a 10.5.0
• 9fd1110 Correct the documentation where it disagreed with the library (#219)
• d478737 Honor the fromURL graceful-failure contract for non-IPv6 hosts (#218)
• fbb8db2 10.4.0
• 45a2b11 Validate the byte arrays Address6 is given (#217)
• bac8810 Keep the package loadable on node 12, and enforce it (#216)
• 9b3d848 Add a security policy and a README section on security posture
• e84a7b3 Order the README API reference Address4, Address6, AddressError
• 015160b Collapse each class in the README API reference
• 34061a8 Pin checkout and setup-node to commits in the release job
• Additional commits viewable in compare view

Maintainer changes

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

Install script changes

This version adds prepare script 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 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[zedarvates]

Root lockfile validation — high-severity ip-address fix

Scope confirmed: this PR changes only root package-lock.json, from ip-address 10.2.0 to 10.5.0.

It addresses open root Dependabot alert #406, GHSA-mwp4-54f8-5fhr / CVE-2026-69192 (high, CVSS v4 7.7): ambiguous leading-zero IPv4 octets can cause resolver/classifier disagreement and SSRF trust-boundary bypass. The first patched version is 10.3.1; 10.5.0 is above that floor.

Verified

• clean npm ci --ignore-scripts succeeded;
• installed dependency chain resolves exactly ip-address@10.5.0;
• root CLI TypeScript build passed;
• Sonar Quality Gate passed with 0 new issues/hotspots.

Limits / blockers

• this PR fixes the named ip-address alert but does not make the root tree clean: npm audit still reports 20 vulnerable packages (17 high, 2 moderate, 1 low), including Electron/build tooling, Axios, Sharp, js-yaml, brace-expansion and shell-quote;
• Electron TypeScript build is blocked by the pre-existing missing/untracked electron/SplashWindow, not by this lockfile change;
• the broad Jest suite exceeded the bounded validation window and left no test process running, so it is not a green test result;
• chore(deps): bump the npm_and_yarn group across 3 directories with 12 updates #31 removes this transitive dependency entirely and reduces the remaining audit count much further, but chore(deps): bump the npm_and_yarn group across 3 directories with 12 updates #31 itself still needs full regression validation.

Keep #32 unmerged until the required complete check matrix exists and is green. It remains a valid surgical fallback for the root high-severity alert.

[zedarvates]

Additional functional proof: with the clean PR #32 install, require('ip-address/package.json').version returns 10.5.0, and Address4.isValid('012.0.0.1') returns false. This directly verifies the leading-zero IPv4 ambiguity used by GHSA-mwp4-54f8-5fhr is rejected in the installed root tree.