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 betaThe Monday refresh
Once a week, Cheer finds components where a newer version would clear an open finding or an end-of-life check, then:
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.
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.
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 automateTwo 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.