Approval-gated Heroku release rollback workflow. It reads the app, target release, and recent releases for context, then calls recued-core.heroku.release.rollback with the documented release body field. It does not create builds, restart or stop dynos, scale formation, mutate config vars, delete resources, or call arbitrary Heroku API routes.

How it works 13 steps

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

Process (13 steps)

■ app_key trim

Trim whitespace from setting app name

■ release_key trim

Trim whitespace from setting target release id

■ reason_text trim

Trim whitespace from setting reason

■ app ?

■ target_release ?

■ releases_before_raw ?

■ rollback ?

■ releases_after_raw ?

■ releases_before default

Apply default

■ releases_after default

Apply default

■ release_rows slice

Take a subset of

■ release_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 4 configurable

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

heroku setting =

reason setting =

app name setting =

target release id setting =