---
updatedAt: 2026-07-21T07:56:27.000Z
agentTools:
  siteIndex: https://docs.jfrog.com/llms.txt
  projectIndex: https://docs.jfrog.com/governance/llms.txt
---

# Create a Draft Release Bundle v2 Version

Learn how draft Release Bundle v2 versions work on the JFrog Platform before you finalize and promote them.

<Callout icon="❗" theme="warn">
  RLM Deprecation

  All feature development, patches, and security fixes for Release Lifecycle Management ended on **July 31, 2026**, except for critical security fixes. RLM End of Life is currently scheduled for **January 31, 2028**. For more information, see <Anchor target="_blank" href="/releases/docs/release-lifecycle-management-deprecation-end-of-life">JFrog Release Lifecycle Management Deprecation - End of Life</Anchor>.
</Callout>

Use the `draft="true"` option in the request body of the [Create Release Bundle v2 Version](/reference/createBundleVersion) REST API to create a draft Release Bundle v2 version. This is an unlocked, mutable bundle to which you can continue adding sources throughout the build process using the [Update Release Bundle v2 Version](/reference/updateBundleVersion) REST API.

When the Release Bundle version has reached its final state, you can use the [Finalize Release Bundle v2 Version](/reference/finalizeBundleVersion) REST API to lock the version and render its contents immutable.

Draft versions allow CI/CD pipelines and developers to create a bundle and modify it as needed to comply with standard, mutable build processes, while preserving the strict immutability required for the final release.

## Limitations

Draft Release Bundle versions are subject to the following limitations:

* You cannot add evidence to a draft Release Bundle version.
* Concurrent updates to the same draft Release Bundle version are handled sequentially. Each request waits for the previous one to complete.
* Any evidence and properties added to artifacts after the artifacts were added to the draft bundle will not be part of the final bundle.
* If a build was modified after it was added to the draft bundle, those changes will not be reflected in the final bundle.
* Draft bundles cannot be scanned by JFrog Xray for vulnerabilities. Scanning is performed only after the draft bundle is finalized.
* If you [promote](/docs/promote-a-release-bundle-v2-version) a draft bundle, it is automatically finalized and locked before it is promoted to the designated stage.

## Related Topics

* [Creating Release Bundles (v2)](/docs/create-release-bundles-v2)
* [Create a Release Bundle v2 using the REST API](/docs/create-a-release-bundle-v2-using-the-rest-api)
* [Create Release Bundle v2 Version REST API](/reference/createBundleVersion)
* [Finalize Release Bundle v2 Version REST API](/reference/finalizeBundleVersion)
* [Promote a Release Bundle v2 Version](/docs/promote-a-release-bundle-v2-version)

<br />