Skip to content
Recued
Menu
← Back to recipes

Record a Sentry release deploy

by recued-core v1

Approval-gated Sentry release deploy marker workflow. It reads the target release for context, then creates exactly one deploy marker through recued-core.sentry.release.deploy.create. It does not create, update, archive, or delete releases; upload files; read project DSNs; or mutate alert configuration.

How it works 3 steps

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

Process (3 steps)
release ?
deploy ?
card to_summary
Format results as a summary card
Settings 8 configurable

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

url setting =
name setting =
sentry setting =
version setting =
environment setting = production
date started setting =
date finished setting =
organization id or slug setting =

Trust & control

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

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

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

About

Tags

sentry sentryreleasedeployciapprovalincident-responsepack:sentry

Details

3 steps 8 configurable settings recipe_id: record-sentry-release-deploy