Routine · Engineering
Dependency update review
A weekly list of outdated packages and the risk of each update.
Runs: Every Monday.
- Risk
- R0 Reads and reports
- Needs
- Dependency list
- A person
- has no approval step by design
On request, as of 4 Nov 2026.
How it works
- Read the dependency list.
- Check each for newer versions.
- Write the list with the riskiest first.
Needs from you: Dependency list.
What it needs connected: Code host, read only.
Where a person is designed to decide: It is designed only to read and report, so it has no approval step.
These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.