Create a Draft Release Bundle v2 Version

❗
RLM Deprecation
As of July 31, 2026, all feature development, patches, and security fixes for Release Lifecycle Management will end, except for critical security fixes. RLM End of Life is currently scheduled for January 31, 2028. For more information, see JFrog Release Lifecycle Management Deprecation - End of Life.

Use the draft="true" option in the request body of the Create Release Bundle v2 Version 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 REST API.

When the Release Bundle version has reached its final state, you can use the Finalize Release Bundle v2 Version 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 a draft bundle, it is automatically finalized and locked before it is promoted to the designated stage.

Limitations

Related Topics