⚙️ [Maintenance]: Dependency updates run independently - #168
Merged
Marius Storhaug (MariusStorhaug) merged 3 commits intoAug 9, 2026
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Marius Storhaug (MariusStorhaug)
marked this pull request as ready for review
August 9, 2026 21:17
This was referenced Aug 15, 2026
Marius Storhaug (MariusStorhaug)
added a commit
that referenced
this pull request
Aug 15, 2026
Dependabot version-update pull requests continue to use the three-day cooldown built into Dependabot, without repository-specific configuration that duplicates the default. ## Changed: Cooldown configuration GitHub Actions and Python dependency updates continue to run at `0 9 * * 1,3,5` in `Europe/Oslo` with their existing labels, and each dependency update remains an independent pull request. --- <details> <summary>Technical details</summary> - Removed the explicit `cooldown.default-days: 3` mappings and their inline Zizmor suppressions from `.github/dependabot.yml`; Dependabot's documented default preserves the same version-update behavior. - Added `.github/linters/zizmor.yaml` to disable only `dependabot-cooldown`: Zizmor 1.25.2 requires an explicit cooldown mapping even when configured with a three-day threshold, so it cannot represent Dependabot's equivalent implicit default. Super-Linter invokes this configuration path directly. - Documented the three-day default and the reason version updates wait in the dependency-update requirement and design and in the GitHub Actions standard. Security updates continue to bypass the cooldown. - Validation: strict offline Zizmor collection using Super-Linter's configuration path for the Dependabot file and the full repository reports no findings; YAML parsing confirms the two update entries retain their schedules and labels and contain neither cooldown nor grouping configuration; documentation-index and link verification, Zensical build, and all 87 Pester tests pass. - Implementation plan progress: all six steps in #173 are complete. - The topic branch is named `remove-dependabot-cooldown` rather than `<type>/<issue>-<slug>` because the required one-time session rename occurred before the delivery Task existed; the Copilot app cannot rename it again or retain a slash. - Issue convergence sweep: searched open MSXOrg/docs issues for `cooldown`; #173 is the only delivery issue fully satisfied by this diff. | Changed surface | Standards checked | Framework docs checked | Result | | --- | --- | --- | --- | | `.github/dependabot.yml` | Dependabot scheduling, labels, and independent-update configuration | Dependency Updates design | Aligned | | `.github/linters/zizmor.yaml` | Zizmor rule configuration and Super-Linter configuration path | None (no framework-specific docs) | Aligned | | `src/docs/Capabilities/dependency-updates/**` | Markdown; Dependency Updates spec and design | Dependency Updates capability | Fixed in this PR | | `src/docs/Coding-Standards/GitHub-Actions.md` | Markdown; GitHub Actions standard | Dependency Updates capability | Fixed in this PR | </details> <details> <summary>Relevant issues (or links)</summary> - Resolves #173 ### Related work - References #168 </details> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Dependency updates now arrive as separate pull requests, making each update independently reviewable and releasable. Dependabot checks run at 09:00 Europe/Oslo on Monday, Wednesday, and Friday, and version updates wait three days after release before being proposed.
Changed: Dependency update cadence and review scope
Each dependency update now has its own pull request rather than being bundled with other minor or patch updates. This keeps release attribution and rollback scope clear for maintainers.
Version-update checks run on Monday, Wednesday, and Friday at 09:00 Europe/Oslo. A three-day cooldown remains in place before Dependabot proposes a newly published version. Security updates continue to bypass the schedule and cooldown.
Technical details
groupsconfiguration for the GitHub Actions and pip ecosystems.0 9 * * 1,3,5schedule with theEurope/Oslotimezone and a three-day default cooldown..github/dependabot.ymlsrc/docs/Coding-Standards/GitHub-Actions.mdsrc/docs/Capabilities/dependency-updates/**Relevant issues (or links)