---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Releases

# Releases in ReleaseOps {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Scheduled and on-demand releases are how changes are deployed to target instances with ReleaseOps. Releases can contain one or more deployment requests.

## Creating a release {#releases-in-release-ops__Toc193701035}

Generally, a release manager is responsible for creating releases and mapping a team or organization's release workflows to a release cadence.

There can be a single release stream or multiple release streams available at any given time. However, only one release can be in the process of deploying to a target instance at any time.  
For example, an organization might have two release tracks that they define:

* A regular weekly cadence for releases, at 10:00 each Friday.
* A daily cadence for high-priority releases, at 12:00 each day.
{#releases-in-release-ops__ul_ypd_lfl_1gc}The weekly and daily release tracks can coexist without issue.

For more information about creating a release, see [Create a release](https://servicenow-prod.fluidtopics.net/2Gq9N1~SLeTZumtFsch5OQ "Specify the details for your release, including the target instance that the changes will be deployed to and when the release should occur.").

## Release types {#releases-in-release-ops__Toc193701036}

Releases that are planned and scheduled in advance are considered scheduled releases. These releases can consist of one or more deployment requests. Each deployment request in the release can include of one or more
update sets.

On-demand releases are created dynamically when the need arises, such as deploying changes to patch a defect in an application. When a developer creates a deployment request and selects the option for an on-demand
release, ReleaseOps dynamically creates a release to drive this request to its target instance. As a result, only one deployment request can be attached to an on-demand release.  
Importante:  
Changes in an on-demand release are intended to be deployed to their target as soon as possible. However, on-demand releases must still pass the checks in the organization's pipeline. Doing so helps to verify that the changes meet the requirements for the organization's compliance and governance policies, as well as quality assurance checks. Once the on-demand request has passed these checks, the deployment proceeds immediately.

ReleaseOps includes deployment analyzer, a tool provided to introspect a deployment. The deployment analyzer enables release administrators to verify that on-demand releases meet certain criteria, such as only
making specific types of code changes. For more information, see [Deployment analyzer in ReleaseOps](https://servicenow-prod.fluidtopics.net/3CwzGTwmbt0UhRgjciteMQ "The deployment analyzer reviews the update set in your release against rules to verify compliance with customizable rules.").