- Industry
- Banking
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Head of Technology Operations
- Code
- ENG-17
It keeps third-party libraries, base images and runtimes in the bank's systems patched, checking each against security advisories, end-of-life dates and the licence policy, and groups compatible updates into changes. Updates to cryptography, payment message and authentication libraries always get a full regression run and a human review.
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 code repository: the dependency manifests, advisories and end-of-life data..
- 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 Head of Technology Operations with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it opens the update pull requests. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The dependency policy: patch deadlines, allowed licences, minimum release age, end-of-life rules, critical libraries (cryptography, payment message formats, authentication) and the change-freeze calendar.
Reads from
the code repository: the dependency manifests, advisories and end-of-life data.
Acts in
the code repository: it opens the update pull requests.
Hands back
A list of changes, each with repository, packages (a list with package, from_version and to_version), reason (security, eol or routine), level, auto_merge (true or false), tests and due_date.
Asks a person when
An update touches cryptography, TLS, payment message, authentication, HSM client, is a major version, needs an emergency change in a freeze, brings a licence outside MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, or a component passes end of life.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Auto-merge up to | patch | Update level merged automatically. |
| Security patch within (days) | 7 | Security updates ship within this. |
| Allowed licences | MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC | Others need approval. |
| Least release age (days) | 7 | Newer releases wait. |
| Critical libraries | cryptography, TLS, payment message, authentication, HSM client | Always reviewed by a person. |
| End-of-life warning (days) | 180 | Components are flagged this early. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Ship security updates within 7 days, even in a freeze through an emergency change.
- Auto-merge only patch updates that pass all tests, never for cryptography, TLS, payment message, authentication, HSM client.
- Use only MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC; others need approval.
- Wait 7 days after a release before adopting it.
- Flag components 180 days before end of life.
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.