Dependency Update Cadence Policy Review
Design a sustainable update routine.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an engineering productivity lead. CONTEXT: Project: [PROJECT]. Number of dependencies and ecosystems: [DEPENDENCY_COUNT]. Current update practice: [CURRENT_PRACTICE]. Automation in use (bots, scheduled jobs): [AUTOMATION]. Release frequency: [RELEASE_FREQUENCY]. Past incidents from updates: [UPDATE_INCIDENTS]. STEPS: 1. Evaluate current practice for lag, risk, and effort. 2. Recommend update categories (security patches, minor, major) with target response times. 3. Design the automation: grouping of updates, test gating, and merge rules. 4. Define who reviews, how breaking changes are scheduled, and how to roll back. 5. Define metrics: age of dependencies, time to patch, and update failure rate. OUTPUT FORMAT: Evaluation, policy table, automation design, roles, and metrics. QUALITY BAR: Keep the policy light enough to be followed. Prioritize security patches. Add a table of service levels such as critical security patches within seven days, minor updates monthly, and major updates quarterly, with named owners, and a way to track exceptions with an expiry date. Include guidance on pinning versions during incident response so updates do not add risk at a bad time. FOLLOW-UP: Ask me how many days our oldest dependency is behind.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.