ci: create dependabot.yml to enable dependabot version updates #19
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.
What does this PR do?
This PR initializes the
dependabot.yml
file for enabling Dependabot version updates. This will auto update npm and GitHub Action dependencies according theauto
version strategy listed here https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy.Background info
The configuration file also affects Dependabot Security updates. In essence, we are proceeding with the default configuration for Dependabot security updates but requiring version updates to be included for npm packages and GitHub Actions. The scans from Dependabot will run on a random time every Monday. PRs that are open will have our team automatically requested to review.
How can this be tested (manually and/or automated test)?
Provide Manual tests Steps if applicable
No code changes have been made. We will monitor how Dependabot makes PRs proposing version updates and modify the configuration as needed.
Provide steps for running automated tests if applicable
N/A
Which issue(s) is/are related to this PR?
This PR is/are related to issue(s) #18
close #18