# Review changes before publishing to Production

> Novu’s new publish dialog shows every change between Development and Production, flags breaking changes and lets you choose exactly what goes live.

Canonical: https://www.novu.co/changelog/review-changes-before-publishing-to-production/

Markdown: https://www.novu.co/changelog/review-changes-before-publishing-to-production.md

Last updated: 2026-11-16T11:27:00.000Z

Novu’s new publish dialog shows every change between Development and Production, flags breaking changes and lets you choose exactly what goes live.

Published: 2026-11-16T11:27:00.000Z

Categories: Improvement, Dashboard

Publishing changes to Production is now easier to review and control. We've redesigned the publishing experience to give you a detailed view of what's changed between Development and Production, so you can identify potential issues and decide what goes live.

Previously, it was difficult to see exactly what would change in Production before publishing. This was particularly risky when modifying existing workflows, where a change to a payload schema or the removal of a step could affect live notifications.

With the new **Publish changes** menu, you can review these differences before publishing.

## **Every change, grouped and labeled**

When you click **Publish changes**, the dialog lists every workflow and layout that’s different between Development and Production. Each workflow is split into steps, payload schema, channel preferences and translations, so you can see where a change sits. Every item is marked **Added**, **Deleted**, **Modified** or **Breaking**. Each one also shows a +/− line count, who changed it and when. The top of the dialog shows how many changes there are in total and how many of them break something.

A collapsed row still shows **Breaking** if anything inside it breaks, so you can scan a long list without opening every row. To find a specific change, use the search box.

## **Breaking changes tell you what will fail**

A breaking change comes with a note about what it will do in Production. Say you make resetUrl a required payload field. The dialog warns you that triggers that don’t send it will fail after you publish. If you delete a workflow, the dialog says it will be removed from Production and shows when it was last triggered. That way you know whether live traffic still uses it.

## **Compare Production and Development side by side**

Open a step and **Preview** shows its Production and Development content next to each other. Switch to **JSON** to read the raw diff instead. Payload schemas show a line-by-line code diff, with unchanged lines collapsed.

## **Publish only what’s ready**

Uncheck anything you’re not ready to ship, and Production keeps it as it is. After you publish, a confirmation lists exactly what’s now live, and new triggers use those versions from then on. Click **Switch to Production** to see the changes there.

## **Get started**

The new publish dialog is available now. Go to your Development environment and click **Publish changes**. You need the Admin or Owner role to publish. To learn more about how publishing works, see the [Environments docs](<https://docs.novu.co/platform/developer/environments#publish-changes-to-other-environments>).
