Understanding Release Bundles v2
Learn how Release Bundles v2 group release artifacts into immutable, signed packages for promotion and distribution through the JFrog Platform.
RLM Deprecation
All feature development, patches, and security fixes for Release Lifecycle Management ended on July 31, 2026, except for critical security fixes. This deprecation removes the ability to promote Release Bundle v2 versions between defined lifecycle stages. It will still be possible to create Release Bundles, add properties and attach evidence, and distribute those Release Bundles to targets such as Edge nodes. RLM End of Life is currently scheduled for January 31, 2028. For more information, see JFrog Release Lifecycle Management Deprecation - End of Life.
Release Bundles group together the contents that comprise the bill of materials for your software releases. Each Release Bundle specifies the files and packages that comprise a release, along with their metadata.
Release Bundles exist as a series of one or more versions, each of which must contain at least one artifact. Release Bundles may include source artifacts from local and Federated Repositories only. A new Release Bundle can be created in several ways, including from builds, individual artifacts, Artifactory Query Language (AQL) queries, or existing Release Bundles.
Note
Release Bundles can't contain source artifacts that share the same path and name from different repositories, which is called a path collision. In such cases, the newer artifact is kept by default.
Since all the artifacts specified in a Release Bundle are required to keep the release coherent, a Release Bundle version is immutable. Effectively, this means that once a Release Bundle version has been created (or a draft version finalized), files can't be added, modified, or deleted. In addition, any subsequent changes to the properties of the source artifacts aren't reflected in the Release Bundle. To change a Release Bundle, you must create a new version.
Each Release Bundle is stored in a Release Bundle repository with a unique name and version per project.
JFrog Artifactory tracks all actions related to the Release Bundle version, including its creation, each time it's promoted to a new environment, and when it's distributed. This transparency helps you trust the process that produced the software release.
Types of Release Bundles
The following sections describe the different types of Release Bundles.
Release Bundles v2
You can use Release Bundles v2 as the vehicle within JFrog Artifactory for creating an immutable set of artifacts for a release. You can optionally promote the release through a defined lifecycle from the build stage through production (see note below), and distribute that release to designated targets like Edge nodes for your end users to access.
Note
The promotion and lifecycle features of Release Bundle v2 will be removed as part of the deprecation of Release Lifecycle Management (RLM), which was announced on July 31, 2026. RLM End of Life is currently scheduled for January 31, 2028. Other Release Bundle v2 features, including creation and distribution, are unaffected by the deprecation.
Release Bundles v2 offer the following advantages over v1:
- Can combine multiple existing Release Bundles into one. This can be used, for example, to merge bundles from multiple microservices into a single release-level bundle.
- Supports the creation of evidence that attests to every action performed on the Release Bundle as a whole, as well as evidence associated with the individual artifacts that comprise the bundle.
- Supports Xray scanning with automatic SBOM creation (CycloneDX/SPDX), including the option to block Release Bundle promotion if the security policy is violated.
- Provides native support for JFrog Projects, which enables administrators and DevOps teams to assign, manage, and control project resources to specific departments, teams, or products.
Release Bundles v1
If you use Enterprise+, you may be familiar with the concept of Release Bundles, which are used exclusively by JFrog Distribution to distribute releases to Edge services located at remote sites. This type of Release Bundle is now known as v1.
Release Bundles v1 do not support JFrog Projects.
Release Bundle v2 Repositories
A Release Bundle v2 is stored as self-contained evidence in a read-only repository with the special package type, ReleaseBundles. The Release Bundle repository is created automatically when the first Release Bundle is created.
The Release Bundle specification is stored as release-bundle.json.evd at {rb-repository-key}/{rb-name}/{rb-version}/release-bundle.json.evd. The file is a DSSE envelope whose payload and signature are Base64-encoded.
In addition to the Release Bundle specification, each Release Bundle contains a snapshot of all included artifacts. Deleting any source artifact from the original path does not compromise the consistency of the contents of the Release Bundle.
The name of the repository used for all Release Bundles created outside the context of a specific project is release-bundles-v2. For project-specific Release Bundles, the following prefix is added to the name: {project-key}-release-bundles-v2.
Note
Any attempt to add a prefix to the Release Bundle repository name that does not match the project name will result in an error.
Release Bundles v2 and Docker Manifests
A Docker manifest is a JSON file that describes image variants for multiple platforms. If source artifacts contain a Docker manifest (manifest.json or list.manifest.json), the manifest is resolved automatically during Release Bundle v2 creation. This means the Release Bundle will include both a manifest and all Docker image layers.
You can disable this behavior using the REST API. For more information, see Create Release Bundle v2 Version.
Frequently Asked Questions
This section provides answers to frequently asked questions.
FAQs
Q: What is the difference between Release Bundles v1 and v2?
A: Release Bundles v1 are distributed to remote Edge services with JFrog Distribution, while Release Bundles v2 are promoted through SDLC environments in JFrog Artifactory with Release Lifecycle Management and optionally distributed with JFrog Distribution. See Types of Release Bundles.
Q: Why are Release Bundle versions immutable?
A: Immutability keeps all artifacts in a release coherent after a version is created or a draft version is finalized. To change contents, you must create a new Release Bundle version. See Release Bundle v2 Repositories.
Q: What is a path collision in a Release Bundle?
A: A path collision occurs when source artifacts from different repositories share the same path and name. Release Bundles can't include both artifacts, so remove the conflict before creation.
Q: Where are Release Bundle v2 repositories stored?
A: Release Bundle v2 is stored in a read-only ReleaseBundles repository created automatically on first use. Global bundles use release-bundles-v2; project-scoped bundles use {project-key}-release-bundles-v2. See Release Bundle v2 Repositories.
Q: How does Release Bundle v2 handle Docker manifests?
A: When source artifacts include manifest.json or list.manifest.json, JFrog Artifactory resolves the manifest and all image layers during creation. You can disable this behavior with the REST API. See Release Bundles v2 and Docker Manifests.
Related Topics
Updated 14 days ago
