Create a Release Bundle v2 using the REST API
Learn which sources the Release Bundle v2 REST API accepts and how fail_safe groups validation errors.
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 Create Release Bundle v2 Version REST API to create a new Release Bundle v2. When you use the API, you can create Release Bundles from one or a combination of the following source types:
- Artifactory Query Language (AQL)
- Artifacts
- Packages
- Builds
- Release Bundles
Release Bundle v2 Creation Errors Collected by System
When you use the REST API for Release Bundle v2 version creation, set the optional query parameter to fail_safe=false to have JFrog Artifactory collect the following validation errors and return them as a group after the failed creation operation:
| Error Code | Sample Errors |
|---|---|
| 400 |
|
| 403 |
|
| 404 |
|
| 422 |
|
Note
The errors listed in the table above are meant to be representative but are not an exhaustive list.
When fail_safe=true (default value), the creation operation will fail as soon as the first validation error is encountered.
Other types of errors, such as 403 errors due to permissions or an expired key and 409 errors due to attempts to create a version that already exists, are not supported by the fail_safe option.
Tip
By default, a maximum of 50 errors are returned. The limit is defined by the system property
lifecycle.errors.group.limit.
Related Topics
- Creating Release Bundles (v2)
- Create Release Bundle v2 Version REST API
- Create a Release Bundle v2 in the JFrog Platform UI
- Release Lifecycle Management Setup
- Understanding Release Bundles v2
Updated 11 days ago