> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duckpost.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Create and publish releases

> Write, preview, schedule, and publish release notes in DuckPost.

<p align="center">
  <img className="rounded-lg" src="https://mintcdn.com/duckpost/aAhMZODiV5dM3w5v/brand/create_release.webp?fit=max&auto=format&n=aAhMZODiV5dM3w5v&q=85&s=52fa4ed9fd19e09f63e5cf5288e95e9d" alt="DuckPost create release editor" width="720" data-path="brand/create_release.webp" />
</p>

DuckPost uses one editor flow for new releases and edits. Start from [**Releases**](https://duckpost.app/releases), then click [**New release**](https://duckpost.app/releases/new).

## What the editor includes

| Field             | Required | Notes                                      |
| ----------------- | -------- | ------------------------------------------ |
| Title             | Yes      | 3 to 100 characters                        |
| Summary           | Yes      | 10 to 240 characters                       |
| Rich text content | Yes      | Must contain visible text                  |
| Release type      | Yes      | Pick the type that best matches the update |
| Cover image       | No       | `PNG`, `JPG`, or `WebP`, up to `5 MB`      |
| Tags              | No       | Reuse existing tags or create new ones     |

## Release types

Use release types to help customers scan your changelog faster:

* `PRODUCT_UPDATE` for general improvements
* `PERFORMANCE` for speed or reliability gains
* `FEATURE` for new customer-facing capabilities
* `BUG` for fixes
* `SECURITY_UPDATE` for security-related work

## Publish workflow

<Steps>
  <Step title="Write the release">
    Add the customer-facing title, summary, details, tags, and release type.
  </Step>

  <Step title="Preview the output">
    Use the editor preview tools to check the public page and widget presentation before you ship.
  </Step>

  <Step title="Choose a publish mode">
    Save as **Draft**, publish immediately, or schedule the release for later.
  </Step>

  <Step title="Decide on notifications">
    Turn subscriber notifications on if confirmed email subscribers and Slack channels should receive the release when it goes live.
  </Step>
</Steps>

## Subscriber notifications

When a release goes live, DuckPost can notify:

* Confirmed email subscribers
* Connected Slack channels

If there are no subscribers, DuckPost still publishes the release. It only skips the outbound delivery.

## Preview surfaces

The editor includes previews so you can review:

* The public changelog layout
* The widget layout
* Desktop and mobile presentation

Use preview before publishing if your release includes a cover image, longer content, or multiple tags.

## Editing published releases

You can reopen an existing release and update it. Be careful when changing public headlines and summaries after publication because customers may already have seen or shared the original version.

<Warning>
  Scheduled releases publish automatically at the selected time. Make sure your DuckPost deployment keeps scheduled publishing enabled and healthy.
</Warning>