- Industry
- Retail
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Engineering Manager
- Code
- ENG-17
It keeps the libraries and runtimes in the storefront, app, commerce services and till software patched, and decides which upgrades to take now, which to batch and which to hold until after peak trading. It opens the upgrade changes with the test results.
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, available updates, advisories and test results for the service..
- 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 Engineering Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it opens or merges the update pull requests as decided. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The dependency policy: the supported versions, the upgrade cadence, the libraries in PCI DSS scope, the peak trading freeze, and the known breaking upgrades.
Reads from
the code repository: the dependency manifests, available updates, advisories and test results for the service.
Acts in
the code repository: it opens or merges the update pull requests as decided.
Hands back
A list with one entry per update, each with package, new_version, decision (merge_now, batch, hold or emergency), reason, tests_passed (true or false) and due_date (YYYY-MM-DD or null).
Asks a person when
The update is major, touches a library in PCI DSS scope or the till software, or applies a security fix in the freeze.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Merge passing patch updates | On | When on, patch updates that pass every test are merged without review, outside the freeze. |
| Security patch deadline (days) | 7 | Updates fixing a known vulnerability are applied within this. |
| Hold major upgrades in peak season | On | When on, major upgrades wait until after the peak trading season. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Apply updates that fix a known vulnerability within 7 days, even in the freeze, through the emergency change process.
- When on is true, merge patch updates that pass every test, outside the freeze.
- When on is true, hold major upgrades until after peak trading.
- Any update to a library in PCI DSS scope or the till software needs the Engineering Manager.
- Batch minor updates per service each fortnight.
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.