Creating Release Bundles (v2)
Learn how to create Release Bundle v2 versions on the JFrog Platform using the UI, REST API, or JFrog CLI, then promote immutable, signed releases with full traceability.
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.
Subscription Information
This feature is supported on the SaaS platform with a Pro, Enterprise X, or Enterprise+ subscription, and on the Self-managed platform with a Pro, Pro X, Enterprise X, or Enterprise+ subscription.
Creating a Release Bundle v2 version on the JFrog Platform produces an immutable, signed set of content with a specified version identifier. After you create a Release Bundle, you can promote it to different environments with full traceability. For more information, see Promote a Release Bundle v2 Version.
Release Bundle v2 Creation Methods
You can create Release Bundle v2 versions using the JFrog Platform UI, REST API, or JFrog CLI. Each method supports different content sources.
| Method | Documentation | Supported sources |
|---|---|---|
| JFrog Platform UI | Create a Release Bundle v2 in the JFrog Platform UI | Builds, other Release Bundles |
| REST API | Create a Release Bundle v2 using the REST API | Builds, Release Bundles, Artifactory Query Language (AQL) query, artifacts, packages |
| JFrog CLI | Create a Release Bundle v2 with the JFrog CLI | Builds, Release Bundles, AQL query, artifacts, packages |
The JFrog Platform UI supports creating Release Bundle v2 versions from builds and other Release Bundles. The REST API and JFrog CLI also support creating Release Bundle v2 versions from an Artifactory Query Language (AQL) query, a list of artifacts, and packages.
Frequently Asked Questions
This section provides answers to frequently asked questions.
FAQs
Q: How do I create a Release Bundle v2 on the JFrog Platform?
A: Choose a creation method in Release Bundle v2 Creation Methods: JFrog Platform UI, REST API, or JFrog CLI. Each method has its own procedure topic with step-by-step instructions.
Q: What is the difference between creating a Release Bundle v2 in the JFrog Platform UI and with the REST API or JFrog CLI?
A: The JFrog Platform UI supports builds and other Release Bundles as sources. The REST API and JFrog CLI support those sources plus AQL queries, artifact lists, and packages. See the comparison table in Release Bundle v2 Creation Methods.
Q: What do I need before I can create and sign a Release Bundle v2?
A: You must create GPG signing keys on the JFrog Platform first. For more information, see Create Signing Keys for Release Bundles v2.
Q: Can I promote a Release Bundle v2 after I create it?
A: Yes. After creation, you can promote the Release Bundle v2 version to different environments with full traceability. For more information, see Promote a Release Bundle v2 Version.
Q: Which JFrog Platform subscriptions support Release Bundle v2 creation?
A: Release Bundle v2 creation is available on SaaS with Pro, Enterprise X, or Enterprise+ subscriptions, and on Self-managed with Pro, Pro X, Enterprise X, or Enterprise+ subscriptions. See the subscription Note at the top of this page.
Related Topics
- Release Lifecycle Management
- Release Lifecycle Management Setup
- Promote a Release Bundle v2 Version
- Understanding Release Bundles v2
- Create a Release Bundle v2 in the JFrog Platform UI
- Distribute Release Bundles v2
Updated 11 days ago