Update Release Bundle v2 Version

patch

https://{jfrog_url}/lifecycle/api/v2/release_bundle

Updates an existing draft Release Bundle v2 version by adding new sources and/or applying filters. The bundle must be in draft state to be updated. You can add sources of any supported type (AQL, Artifacts, Packages, Builds, or Release Bundles) and optionally apply inclusion/exclusion filters.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Query Params

async

boolean

Defaults to true

Whether to update the bundle asynchronously

fail_fast

boolean

Defaults to true

Whether to fail fast on errors

dry_run

boolean

Defaults to false

Whether to perform a dry run without actually updating the bundle

project

string

The project key used to determine the Release Bundles repository. By convention, each project may contain only one Release Bundles system repository with the name <project-key>-release-bundles-v2. This query parameter may be used instead of repository_key.

repository_key

string

The Release Bundles repository identifier that identifies where a Release Bundle version resides. If this parameter and the project query parameter are not specified, the default value of release-bundles-v2 is assumed.

Body Params

Release bundle update request containing bundle name, version, sources to add, and optional filters

release_bundle_name

string

required

Release bundle name. Must begin with a letter, underscore, or digit and consist of letters, underscores, dots, hyphens, or digits.

release_bundle_version

string

required

Release bundle version. Must begin with a letter, underscore, or digit and consist of letters, underscores, dots, hyphens, plus signs, or digits.

add_sources

array of objects

List of source configurations to add to the existing draft bundle. Each source object structure depends on the source_type (aql, builds, artifacts, release_bundles, packages).

add_sources

filters

object

Filters to include or exclude specific artifacts from the bundle

Headers

X-JFrog-Signing-Key-Name

string

length ≤ 255

The name of the signing key to use for signing the release bundle

Responses

200Updated - The Release Bundle version was updated successfully.

400Bad Request - The request body is malformed or a required parameter is missing.

401Bad Credentials - Authentication failed. A valid token is required.

403Permission Denied - The user does not have write permissions for the target repository.

404Not Found - The specified Release Bundle version or a source resource could not be found. The bundle must exist and be in draft state.