fix(dependabot): scope .release to direct dependencies only#36
Merged
Conversation
After #35 isolated the release tooling in .release/, Dependabot's security scan walked the new lockfile and tried to create a security update for brace-expansion inside `node_modules/npm/node_modules/`. That path is bundled by the npm CLI tarball and cannot be bumped independently, so the run failed with `unknown_error`. Add a second `npm` entry for /.release with `allow: dependency-type: direct` so Dependabot only considers direct deps (semantic-release, @semantic-release/changelog, @semantic-release/git) there. Transitive advisories inside npm's own bundled node_modules are out of scope for both us and Dependabot; they land upstream via npm/cli releases.
|
🎉 This PR is included in version 0.6.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
After PR #35 landed the
.release/subpackage, Dependabot's security scan walked.release/package-lock.json, found the bundledbrace-expansioninsidenode_modules/npm/node_modules/, and tried to create a security update PR for it. That path cannot be bumped by us; it lives inside the npm CLI tarball.Result: the Dependabot Updates workflow failed twice with
unknown_error.This PR adds a second
npmentry for/.releasewithallow: dependency-type: directso Dependabot only considers direct deps (semantic-release,@semantic-release/changelog,@semantic-release/git) there. Transitive advisories inside npm's own bundlednode_modules/stay out of scope; they land upstream via npm/cli releases (11.13.0 currently in flight, npm/cli#9240).Test plan