---
updatedAt: 2026-09-09T06:54:58.000Z
agentTools:
  siteIndex: https://docs.jfrog.com/llms.txt
  projectIndex: https://docs.jfrog.com/governance/llms.txt
---

# Distributing Release Bundles v2

Learn how to distribute Release Bundle v2 versions to Edge nodes using the Platform UI, REST API, or JFrog CLI.

<Callout icon="❗" theme="warn">
  RLM Deprecation

  All feature development, patches, and security fixes for Release Lifecycle Management ended on **July 31, 2026**, except for critical security fixes. RLM End of Life is currently scheduled for **January 31, 2028**. For more information, see <Anchor target="_blank" href="/releases/docs/release-lifecycle-management-deprecation-end-of-life">JFrog Release Lifecycle Management Deprecation - End of Life</Anchor>.
</Callout>

<Callout icon="📘" theme="info">
  **Subscription Information**

  This feature is supported with the **Enterprise+** license.
</Callout>

<Callout icon="📘" theme="info">
  **Note**

  This section describes how to distribute Release Bundles v2. For instructions about distributing Release Bundles v1, see <Anchor target="_blank" href="/artifactory/docs/distribute-release-bundles-v1">Distribute Release Bundles (v1)</Anchor>.
</Callout>

After you create a [Release Bundle v2](/docs/understanding-release-bundles-v2) version and promote it through the stages of your SDLC as needed, you can use JFrog Distribution to distribute it to targets to which you have distribution privileges, for example <Anchor target="_blank" href="/artifactory/docs/hybrid-deployment#hybrid-distribution-from-jfrog-platform-self-hosted">Edge nodes</Anchor>.

You can distribute Release Bundle v2 versions using one of the following methods:

* [REST API](/docs/distribute-a-release-bundle-v2-using-rest-apis)
* <Anchor target="_blank" href="/artifactory/docs/distribution-through-cli">JFrog CLI</Anchor>
* [Platform UI](/docs/distribute-a-release-bundle-v2-version-using-the-platform-ui)

JFrog Distribution triggers the replication process from the source JFrog Artifactory to the Edge nodes. First, it replicates the Release Bundle information to each Edge node and then initiates the replication process in the source Artifactory. For more details, see <Anchor target="_blank" href="/artifactory/docs/the-distribution-flow">The Distribution Flow</Anchor>.

## Prerequisites

* The signing key defined in Artifactory must be propagated to the Edge nodes. See [Propagate Signing Keys](/docs/release-lifecycle-management-setup#propagate-signing-keys).

<Callout icon="⚠️" theme="warning">
  **Warning**

  The signing key must be valid. The operation fails if the key has expired.
</Callout>

* Artifactory and the Edge nodes can be connected using one of the following methods:

  * <Anchor target="_blank" href="/administration/docs/access-tokens#generate-scoped-tokens">Using Scoped Tokens (Pairing Tokens)</Anchor>: The JFrog Platform scoped tokens function connects the source Artifactory and the Edge nodes. This is the default option used to connect the source and node. If you cannot upgrade your self-hosted instance, or need to continue using the Circle of Trust, see the next method.
  * <Anchor target="_blank" href="/administration/docs/access-tokens#circle-of-trust-cross-instance-authentication">Circle of Trust</Anchor>: A circle of trust between your source Artifactory and the Edge nodes applies to both the source and target Artifactory nodes.

## Related Topics

* [Distribute a Release Bundle v2 Version Using the Platform UI](/docs/distribute-a-release-bundle-v2-version-using-the-platform-ui)
* [Distribute a Release Bundle v2 Using REST APIs](/docs/distribute-a-release-bundle-v2-using-rest-apis)
* [Distribute a Release Bundle v2 (CLI)](/docs/release-lifecycle-management-cli#distribute-a-release-bundle-v2)
* [Release Lifecycle Management](/docs/release-lifecycle-management)