Repository navigation
Have Dependabot update d3_graph_generator's npm packages - #124
Merged
Merged
Conversation
Dependabot updated the gem's bundler dependencies and its actions, but not the packages of the graph app in d3_graph_generator/, such as vite and react. The npm entry points at that directory, whose yarn.lock is tracked, and takes the same monthly schedule, single group and 7-day cooldown as the other entries. spec/sample_app1 also has a Gemfile and Gemfile.lock, but it is a fixture for the specs, so it's left out.
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
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.
npmentry to.github/dependabot.ymlford3_graph_generator/, so Dependabot updates the graph app's packages (vite, react, d3), not just the gem's dependencies and actions.yarn.lockis tracked.spec/sample_app1has its own Gemfile and Gemfile.lock, but it's a fixture for the specs, so it's left out.