- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Head of Hotel Technology
- Code
- ENG-17
It keeps the libraries, base images, runtimes and payment SDKs used by the booking engine, guest app and hotel integrations patched: it checks each against security advisories, end-of-life dates and the licence policy, groups compatible updates, and opens upgrade changes the booking journey tests must pass. It decides which updates to take now, batch, defer or hold, and holds major versions, payment SDK changes 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 current versions, advisories, end-of-life dates and licences for the codebases 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 Head of Hotel Technology with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it opens upgrade pull requests for the updates taken. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The dependency policy: allowed licences, patch timelines, the payment SDK and PCI DSS rules, runtime end-of-life dates, and the release freezes.
Reads from
the package registry and advisory feed: the current versions, advisories, end-of-life dates and licences for the codebases named.
Acts in
the code repository: it opens upgrade pull requests for the updates taken.
Hands back
A list, each with package, codebase, from_version, to_version, kind, decision (take_now, batch, defer or hold), reason and advisory (id or null).
Asks a person when
The update is a major version, changes a payment SDK while on is true, introduces a licence outside MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, or patches a security advisory in card-data scope.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Highest update it may merge after tests | patch | Updates above this wait for review. |
| Days to take a security patch | 7 | A patch for a known advisory is taken within this. |
| Allowed licences | MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC | A dependency under any other licence is held. |
| Wait after a release before taking it (days) | 3 | Except security patches. |
| Payment SDK updates need review | On | When on, any change to the payment provider's SDK waits for review whatever its level. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Take security patches within 7 days; take others only after 3 days.
- Merge updates up to patch when the booking journey tests pass; anything above waits for review.
- Hold any dependency whose licence is not in MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC.
- When on is true, hold payment SDK and card tokenisation library updates for the Head of Hotel Technology.
- Group compatible updates per codebase and defer non-security updates during release freezes.
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.