---
updatedAt: 2026-07-21T07:55:48.000Z
agentTools:
  siteIndex: https://docs.jfrog.com/llms.txt
  projectIndex: https://docs.jfrog.com/governance/llms.txt
---

# Patch a Release Bundle v2 Version

Learn how to patch a Release Bundle v2 version using included and excluded REST API filters on the JFrog Platform.

<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>

Since [Release Bundle v2](/docs/understanding-release-bundles-v2) versions are designed to be immutable, any modification theoretically requires creating a new Release Bundle v2 version. For example, in a bundle containing hundreds of artifacts, upgrading a single library would traditionally require rebuilding the entire bundle from scratch.

Patching provides greater speed and flexibility by enabling you to take an existing Release Bundle v2 version and create a new version by applying specific changes to it, such as additions, removals, and replacements. Instead of redefining the entire contents of the Release Bundle, you only need to define the changes.

To patch a Release Bundle v2 version, use the optional `included` and `excluded` filters in the [Create Release Bundle v2 Version](/reference/createBundleVersion) REST API. For example:

```json
{
    "release_bundle_name": "A",
    "release_bundle_version": "3",
    "sources": [
        {
            "source_type": "release_bundles",
            "release_bundles": [
                {
                    "project_key": "default",
                    "repository_key": "release-bundles-v2",
                    "release_bundle_name": "A",
                    "release_bundle_version": "2"
                }
            ]
        }
    ],
    "filters": {
        "included": [
            {
                "package_type": "docker"
            },
            {
                "package_type": "generic"
            }
        ],
        "excluded": [
            {
                "path": "**/*.png"
            }
        ]
    }
}
```

In the example shown above, the new version of the Release Bundle (version 3) is based on the current version (version 2), but with the following changes:

* Docker and generic packages will be included.
* Any PNG files included in the current Release Bundle version will be removed.

## Related Topics

* [Creating Release Bundles (v2)](/docs/create-release-bundles-v2)
* [Create a Release Bundle v2 using the REST API](/docs/create-a-release-bundle-v2-using-the-rest-api)
* [Understanding Release Bundles v2](/docs/understanding-release-bundles-v2)
* [Create a Release Bundle v2 in the JFrog Platform UI](/docs/create-a-release-bundle-v2-in-the-platform-ui)

<br />