Clarify Dependabot cooldown wording in tutorial#43799
Clarify Dependabot cooldown wording in tutorial#43799atharvasingh7007 wants to merge 1 commit intogithub:mainfrom
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
@atharvasingh7007 Sorry, the original contributor who opened that issue also opened the PR that resolved it. I hadn't labeled it with "help wanted" yet because I wanted to confirm the wording with him, and then he opened the PR and I didn't need to. I'm going to close this one since it's redundant. |
Summary
cooldownwith the Dependabot options referencecooldowndefines a cooldown period for dependency updatescooldownapplies to version updates, not security updatesCloses #43708.
Validation
npm run lint-content -- --paths content/code-security/tutorials/secure-your-dependencies/optimizing-pr-creation-version-updates.md