Recued
Menu
← Back to recipes

Heroku release investigation brief

by recued-core v1 7 views

Use “Heroku release investigation brief” in Recued. It provides a read-only investigation brief for one Heroku release.

How it works 16 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (16 steps)
app_key trim
Trim whitespace from setting app name
release_key trim
Trim whitespace from setting release id or version
app ?
target_release ?
releases_raw ?
builds_raw ?
dynos_raw ?
formation_raw ?
domains_raw ?
defaults defaults
Apply defaults
summarize ?
release_rows slice
Take a subset of
build_rows slice
Take a subset of
release_table to_table
Format results as a data table
build_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Investigate this Heroku release using only the provided data. Explain status, current/rollback eligibility, adjacent release context, build signals, runtime/domain implications, and concrete next checks.
heroku setting =
app name setting =
row limit setting = 12
max length setting = 900
release id or version setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Heroku connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

heroku herokureleaseincident-reviewrollback-readinessai-summarypack:heroku

Details

16 steps 6 configurable settings recipe_id: release-investigation-brief-heroku