Product · Automations

Let Cheer settle the boring bits

Cheer runs jobs in the same sandbox it analyses in, so it can build a fix and check it against your policy before anyone looks at it. A dependency bot can’t do that.

Join the private beta
Acme Engineering
Overview
Health
Release
Policies
212 of 500 runs this month
InboxMonday 28 Sept, 07:10
Two things need you. The refresh ran overnight on 31 components and opened 3 pull requests.
Compiled by AI from the live record.
Needs youoldest first
Mergepayments-api · Refresh’s ready. 9 upgrades, built and checked. Clears 3 findings.PR 2150
Renewledger-worker · Your waiver of jackson-databind runs out Thursday. Renew or let it go.R. Chen
Refresh · payments-apiran 03:12, took 6 min
Built9 upgrades applied in a fresh sandbox. Build passed, 412 tests passed.03:14
Checked12 checks against the payments policy. 12 cleared. Clears CVE-2026-21744 and two Minor findings.03:17
OpenedPR 2150 with the manifest attached. Nothing else changed.03:18
Left outnotify-svc · axios 2.0 broke the build. Kept out of your queue, with the log.03:20
The first preset

The Monday refresh

Once a week, Cheer finds components where a newer version would clear an open finding or an end-of-life check, then:

1Apply the upgrades in a fresh sandbox, build, run the tests.
2Check the result against that component’s policy.
3Open one PR per component, only if it would be cleared, with the manifest attached.
4Put anything that broke aside with the log, out of your queue.
5Put waivers that are about to expire in the Inbox to renew or retire.
Refresh · Monday 03:0031 components
payments-api · 9 upgrades, clears 3 findingsPR opened
web-gateway · 2 upgrades, clears the undici advisoryPR opened
inventory-sync · 1 upgrade, runtime leaves end of lifePR opened
notify-svc · axios 2.0 broke the buildLeft out
27 components had nothing worth doing. Too easy.
Waivers

Waivers expire on a date you set

When you waive a finding you set how long for. When the date comes, Cheer asks once: renew it or let it go. Nothing stays waived silently, and you are not reminded before the date.

That is what keeps the Inbox short. Nobody decides the same thing twice.

jackson-databind · MajorWaived
Onledger-worker
ByR. Chen, 14 Aug
Why“Not on the request path.”
UntilThursday 2 Oct
Runs out in 3 days.Let it goRenew a month
The rule

What automations can and can’t do

Automations can check, prepare, notify and expire. They can’t waive, approve or present a version at a gate. Neither can an agent.

A machine can hand you something finished. A person says yes to it.

An automation canCheck a version against policyBuild and test an upgradeOpen a pull requestTell someoneLet an waiver run out
It can’tWaive a findingWaive a holdApprove a versionPresent at a gateChange a policy
Where we are

One preset today, more as we learn

The refresh is shipped. We would rather watch how teams use it than guess at the next five.

The likely next one is runtime upgrade drafts for components nearing end of life. If you need that, tell us.

Tell us what you’d automate
AutomationsManage · payments-api
Monday refresh · weekly, 03:00 · opens a PR only if it’d clearOn
End-of-life runtime upgradesComing
Automations run in your quota. A refresh that finds nothing to do costs nothing.

Two upgrades that matter, not a dozen bot PRs

The refresh is one switch per component. Beta teams turn it on for one component first and see what Monday looks like.

Inbox0 items
Nothing needs you. Knock off.