Dependency Upgrades & Patching

A dependency inventory, an upgrade policy, an update bot that does not drown you and the weekly, monthly and quarterly routines that keep libraries, frameworks and runtimes current and patched fast.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Dependency Upgrades & Patching, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Dependency Upgrades & Patching

Keeping libraries, frameworks and runtimes up to date, handling breaking changes and responding quickly to vulnerable dependencies.

  1. Dependency inventory across every repository
  2. Lockfiles committed in every repository
  3. Runtime and framework end-of-life calendar
  4. Owners for shared libraries and internal packages
  5. Dependency freshness baseline in libyears
  6. Written dependency upgrade policy for the team
  7. Vulnerability alert routing to a named owner
  8. Automated update bot on a pilot repository
  9. Checklist for adding a new dependency
  10. Weekly triage of update pull requests
  11. Monthly patch day for minor and patch updates
  12. Vulnerability advisory response routine
  13. Quarterly major version upgrade planning
  14. Container base image refresh routine
  15. Yearly runtime version rollover
  16. Update bot noise and grouping tuning
  17. Monthly dependency health dashboard
  18. Rotating dependency steward each week
  19. Vulnerability exceptions register with expiry dates
  20. Reading changelogs and migration guides well
  21. Semantic versioning and version range syntax
  22. Understanding the transitive dependency tree
  23. Reading an advisory and judging real exposure
  24. Codemods for mechanical upgrade changes
  25. Bisecting a regression introduced by an upgrade
  26. Overrides and resolutions without leaving a mess
  27. Auto-merge rules for low-risk updates
  28. Choosing an automated dependency update tool
  29. Replacing an abandoned dependency
  30. Removing unused dependencies
  31. Pinning strategy for applications and libraries
  32. Private registry proxy and package cache
  33. Collapsing duplicate versions of one package
  34. Fork, vendor or wait decision for a stuck fix
  35. Zero-day drill for a core library
  36. Framework major version upgrade
  37. Runtime end-of-life migration before the cut-off
  38. Catch-up sprint for a stale repository
  39. Annual dependency audit for customers and auditors
  40. Patching during a release freeze
  41. Dependency upkeep for a solo engineer
  42. Coordinated upgrade of a library shared by many teams
  43. Patching a mobile app with slow user updates
  44. Patch bulletins for customer-hosted deployments
  45. First dependency upgrade for a new joiner
  46. Software bill of materials on every build
  47. Package integrity and supply chain checks
  48. Reachability analysis to cut advisory noise
  49. Backporting a security fix to an old release line
  50. Upstream fix for a dependency you rely on

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Dependency inventory across every repository

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. You cannot patch what you do not know you run, and most teams discover their real dependency list during an incident. A single inventory of every repository, its package managers, runtimes, base images and direct dependencies turns the next advisory from a day of grepping into a five-minute lookup.

First tasks

  • List every repository the team owns from the code host's organisation page
  • Export the dependency graph or manifest files for each active repository
  • Record runtime versions and container base image tags beside each service
  • Add new repositories and retire archived ones in the inventory @recurring(quarterly)

Lockfiles committed in every repository

Without a committed lockfile, two builds of the same commit can pull different versions, and a bad release upstream reaches production without anyone changing a line. Committing lockfiles everywhere makes builds reproducible, makes every version change a visible diff in review, and gives the update bot something precise to change. It is the cheapest safety step in the whole area.

First tasks

  • Check each repository in the inventory for a committed lockfile
  • Generate and commit lockfiles where they are missing
  • Switch pipeline installs to the frozen lockfile mode
  • Add a lockfile review rule to the contributing guide

Runtime and framework end-of-life calendar

Language runtimes, frameworks, databases and operating system images all publish end-of-life dates, and after that date security fixes simply stop. A calendar of every end-of-life date that touches your stack gives you a year of warning instead of a week, which is the difference between a planned upgrade and a scramble. Most teams find at least one component already past its date the first time they look.

First tasks

  • Look up the support policy for each runtime and framework in the inventory
  • Flag anything already past end of life to the team lead @priority(high)
  • Add each end-of-life date to the team calendar with a six-month reminder
  • Check the calendar for end-of-life dates in the next six months @recurring(monthly:3)

Make it yours.

Install Dependency Upgrades & Patching, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.