fix(deps): ignore unreachable ip-address advisory in dependabot config - #69
Merged
Merged
Conversation
Dependabot's daily Security job has failed identically since at least 2026-08-04 (security_update_not_possible: latest-resolvable-version 10.2.0, lowest-non-vulnerable-version 10.3.1). Same root cause as node-ninjaone#66: ip-address is nested 3 deep via @semantic-release/npm -> npm (bundled) -> socks -> ip-address@10.2.0, and npm bundles its entire dependency tree at publish time, so it's unreachable from this repo's own dependency graph (verified empirically on node-ninjaone, not re-tested per-repo since the chain is byte-identical across this shared template). Ignoring it in dependabot.yml (dated comment explaining why + how to revisit) so the doomed daily retry stops failing CI. The underlying GHSA alert stays open/visible on the repo's Security tab — this only stops the unreachable PR-open attempt, not the vulnerability tracking.
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 6, 2026
## [3.0.2](v3.0.1...v3.0.2) (2026-08-06) ### Bug Fixes * **deps:** ignore unreachable ip-address advisory in dependabot config ([#69](#69)) ([40d3bb4](40d3bb4))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Dependabot's daily Security job fails identically every day (
security_update_not_possible,latest-resolvable-version: 10.2.0,lowest-non-vulnerable-version: 10.3.1). Same root cause as node-ninjaone#66 (this org's pilot fix):ip-addressis nested 3 deep via@semantic-release/npm→npm(bundled) →socks→ip-address@10.2.0.Why this cant be fixed with a manifest change
npm's published package shipsbundleDependenciescovering its entire tree, so its vendored/pre-resolved at publish time — not resolved through the consuming project's normal dependency graph. Verified empirically on the pilot repo (node-ninjaone): apackage.jsonoverridespin forip-address >=10.3.1had zero effect afternpm install—node_modules/npm/node_modules/ip-addressstayed at10.2.0. This repo shares the identical dependabot.yml template and dependency chain, confirmed via the identical error text in its own failed Security run.Change
Adds the same
ignorerule forip-addressused in the pilot, with the dated explanatory comment. Stops the doomed daily retry from failing CI. Does not dismiss the underlying GHSA alert, which stays open/visible on the repos Security tab.Part of a fleet-wide propagation (boss-authorized) of the pilot fix across 6 repos sharing this template.
🤖 Generated with murph