What a release contains

Creating a release copies three things from the project and stores them under a version number, together with optional release notes.

Stored with every release

Packages The package versions selected for the release, from the built-in feed or your own feeds.
Variables The project's variables and their scoped values when the release was created. Each deployment picks the values for its environment.
Deployment steps The ordered steps, their scripts and their scoping. Later edits to the project don't change existing releases.

Promotion runs the same release

Promoting release 2026.5.16 from Staging to Production deploys the same packages and steps. Only the environment-scoped variable values change. A sign-off in Staging therefore applies to what reaches Production, and rolling back means deploying the previous release again.

A release only covers what Jaws Deploy manages. Database contents, OS patch levels and third-party APIs can still differ between environments.

Versions

Release versions follow SemVer 2.0, so 1.4.2, 2.0.0-rc.1 and 2026.5.16+build.4218 are all valid. Most teams let the CI build choose the version and create the release right after a successful build.

Creating a release from CI

From TeamCity, GitHub Actions, Jenkins or another CI server, with the PowerShell SDK:

Import-Module ./JawsDeploySdk.psm1   # github.com/JawsDeploy/powershell-sdk

# JAWS_API_LOGIN (service account ID) and JAWS_API_PASSWORD (API key)
# come from the CI secret store.

$release = New-JawsRelease `
    -projectId       "<project id>" `
    -version         "2026.5.16.$env:BUILD_NUMBER" `
    -packageVersions @{ "Checkout.Web" = "2026.5.16" } `
    -notes           (Get-Content ./CHANGELOG.md -Raw)

# optional: start the first deployment straight away
Invoke-JawsDeployRelease -releaseId $release.releaseId -environmentName "Dev"

Lifecycles and channels

A lifecycle lists the phases a release passes through, for example Development, then Staging, then Production. A phase can require all of its environments to succeed, a minimum number of them, or be optional. Each environment in a phase is deployed to automatically when the release reaches it, or by hand.

Channels let one project use more than one lifecycle. A hotfix channel can use a shorter lifecycle that starts at Staging while normal releases go through every phase. Channel rules can also limit which release versions and package versions a channel accepts.

Deploying and promoting

Deploy or promote from the UI, the REST API or the PowerShell SDK (Invoke-JawsDeployRelease, Invoke-PromoteRelease). Jaws Deploy checks the lifecycle before each deployment. A release can be deployed to the same environment more than once, for example to re-run it after fixing a server.