# Canary Rollout block

> Deploy rollout sheet with a live canary pipeline, streaming logs and health charts

Release drawer for a canary in flight: Promote, Roll back and Pause controls, error rate and latency against the baseline, and the release's commits. ReUI CodeBlock, Frame, Alert, Badge; shadcn Sheet, Tabs, Chart, AlertDialog. Progressive delivery.

- Type: Pro block
- Category: [Sheet](https://web.dev.reui.io/blocks/application/sheet.md)
- Page: https://web.dev.reui.io/blocks/application/sheet/sheet-15
- Docs (Base UI): https://ui.shadcn.com/docs/components/base/sheet.md
- Docs (Radix UI): https://ui.shadcn.com/docs/components/radix/sheet.md
- MCP: `get_block("sheet-15")`
- Built with: Alert, Alert Dialog, Avatar, Badge, Button, Chart, Code Block, Empty, Frame, Icon Tile, Item, Kbd, Marker, Progress, Sheet, Spinner, Tabs, Toggle, Tooltip
- Installs with a ReUI Pro or Ultimate license; setup: https://web.dev.reui.io/docs/license-setup

## Best for

A live production canary opened on its Pipeline tab, a ticking demo clock advancing the stages, and Undo after each Promote or Roll back

## Agent notes

- `DEPLOYMENTS` in the data file seeds every rollout and `INITIAL_ID` picks the one the sheet opens on; replace both with your release API
- A `setInterval` dispatching `tick` every `TICK_MS` advances the demo clock behind the stages; replace it with real deploy status
- Promote and Roll back dispatch to `consoleReducer` from `confirmAction` and Pause from `pause`, with no API call; wire your release service there

## When not to use

- A finished or failed deploy that needs the full log and a retry: use [Failed Deploy](https://web.dev.reui.io/blocks/application/sheet/sheet-16.md) (`get_block("sheet-16")`)
- Error budget burn rates and alert rules for a service objective: use [SLO Error Budget](https://web.dev.reui.io/blocks/application/sheet/sheet-20.md) (`get_block("sheet-20")`)

## Third-party libraries

- Recharts v3: [API reference](https://recharts.github.io/en-US/api/), [docs](https://recharts.github.io/en-US/guide/getting-started/)
- Sonner v2: [API reference](https://sonner.emilkowal.ski/toast), [docs](https://sonner.emilkowal.ski/getting-started)
- Shiki v4: [API reference](https://shiki.style/guide/install), [docs](https://shiki.style/guide/), through ReUI Code Block

## Install

```bash
npx shadcn@latest add @reui/sheet-15
```

## About Sheet blocks

### When to use

- Record detail opened over a list or table: a ticket, metric, cron job, audit event, deploy, SLO or data source
- Create and edit forms in a side panel for a project, cron job, firewall rule, SLO or data connection
- Utility panels for help guides, keyboard shortcuts, an AI assistant, comments, notifications or view settings

### When not to use

- A bare side panel with your own header, body and footer, nothing prebuilt: use [Sheet](https://web.dev.reui.io/components/sheet.md) (`get_component("sheet")`)
- A persistent sidebar or navigation layout that stays around every page: use the [App Shell blocks](https://web.dev.reui.io/blocks/application/app-shell.md)
- An assistant conversation that fills the whole page rather than a side panel: use the [AI Chat blocks](https://web.dev.reui.io/blocks/ai-agents/ai-chat.md)

### Agent notes

- Each root renders a demo `SheetTrigger` button and opens on mount via `defaultOpen` or a `useState` seeded true; start it closed in your app
- Each `SheetContent` className floats it inset with `inset-y-4`, `right-4` and `rounded-xl` and sets its own width; resize it there, not in the primitive
- Each page.tsx only centers the trigger in a `min-h-svh` main with an `sr-only` h1; render the root component alone inside your page

Every ReUI item has a twin like this one; the index is https://web.dev.reui.io/llms.txt. Agents with the ReUI MCP (https://web.dev.reui.io/docs/mcp) get the same guidance from the getters named above.