- Industry
- Procure AI
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Platform Tech Lead
- Code
- ENG-17
It keeps the platform's third-party libraries, base images and runtimes patched, including the document-parsing, PDF and XML libraries the invoice ingestion depends on, checking each against advisories, end-of-life dates and the licence policy, grouping compatible updates and opening upgrade changes the test suite must pass. It decides which updates to take now, batch, defer or hold, and holds major versions and licence changes for approval.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the package registry and advisory feed: the latest versions, release dates, licences and security advisories for the packages in the repositories named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Platform Tech Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it opens grouped update pull requests and turns on auto-merge where the policy allows. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The dependency policy: the approved licence list, supported runtime versions and end-of-life dates, the update cadence, the packages pinned for e-invoicing format or tax-calculation reasons, and the deployment freeze around client month-end.
Reads from
the package registry and advisory feed: the latest versions, release dates, licences and security advisories for the packages in the repositories named.
Acts in
the code repository: it opens grouped update pull requests and turns on auto-merge where the policy allows.
Hands back
A list with one entry per package, each with repo, package, ecosystem, from_version, to_version, kind (patch, minor or major), reason, advisories_fixed (a list), licence, breaking_notes (text or null) and choice (now, batch, defer or hold).
Asks a person when
An update is a major version, moves a package outside MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, touches a pinned package, or adopts a release younger than 3 days.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Updates merged when tests pass | patch | Updates at this level or below merge once the full suite, including control tests, passes. |
| Days to patch a high or critical advisory | 7 | A high or critical advisory with a fixed version is patched within this long. |
| Licences allowed | MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC | Comma-separated. An update that moves a package to another licence is held. |
| Youngest release adopted (days) | 3 | Releases younger than this are not adopted, except to fix a critical advisory. |
| Most updates per change | 10 | Compatible updates are grouped up to this many per pull request. |
| Warn before end of life (days) | 90 | Anything reaching end of life within this long is planned for upgrade. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Patch a high or critical advisory with a fixed version within 7 days, ahead of all routine updates, with document-parsing libraries first because they read untrusted supplier files.
- Adopt no release younger than 3 days, unless it fixes a critical advisory.
- Hold any update that moves a package outside MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, and any package pinned for e-invoicing format or tax-calculation reasons, until its format tests are re-run.
- Group compatible updates up to 10 per change; a major version gets its own change with its breaking notes.
- Merge updates at patch or below only when the full suite passes, never on a red build and never in the month-end freeze.
- Plan the upgrade of anything reaching end of life within 90 days.
See the Dependency Management Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.