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

[dependabot]

Bumps ip-address from 10.2.0 to 10.4.0.

Release notes

Sourced from ip-address's releases.

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

• 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
• c5fae5d Pin action-gh-release to a commit and move it to 3.0.2
• e0ef048 Replace CircleCI with GitHub Actions
• 5e3ceb7 Add GitHub Actions CI across Node 20, 22, 24 and 25 (#213)
• 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.

[joshuanapoli]

Summary

Lockfile-only bump of ip-address 10.2.0 → 10.4.0. The substantive change is beaugunderson/ip-address#217, which validates the byte arrays handed to Address6 instead of trusting them — the malformed-input hardening this advisory is about.

Risks

Low.

• ip-address is not declared in package.json; it is a transitive dependency, so we have no first-party call sites that could be affected by the new Address6 byte-array validation.
• 10.2.0 → 10.4.0 is a minor bump. The release notes between these versions contain no API removals or renames: CI infrastructure changes, a Node 12 loadability guard, a security policy, and the Address6 validation fix.
• The one behavioral change — Address6 now throwing AddressError on byte arrays that were previously accepted — only fires on input that was already invalid.

Analysis

• Confirmed the diff touches the lockfile only, with no package.json constraint change.
• Confirmed ip-address is transitive, not a declared dependency.
• Read the 10.2.1 → 10.4.0 release notes and commit list for interface changes; found none that our code could depend on.
• Noted the maintainer-change flag in the Dependabot report: the package is now published by GitHub Actions rather than the maintainer's personal account. The commits are all from the repository owner and the change is consistent with the CI migration in the same release, so this reads as a release-automation move rather than a takeover.
• CI is green.