---
title: "How can I use \"Release ref pattern\" for connected repositories in the Ketryx project settings?"
description: "Versioning items can be important when using Ketryx. Point-wise items will only appear in the version they are marked with, and long-lived items will appear in all versions from their introduction to their obsolescence (more on that here)."
category: "Frequently Asked Questions"
section: "Supply Chain Management Software Dependencies"
keywords: ["connected repositories", "ref", "repositories settings", "pattern", "settings release", "dependencies git", "release version", "release release"]
source_url: "https://support.ketryx.com/hc/en-us/articles/30926144259725-How-can-I-use-Release-ref-pattern-for-connected-repositories-in-the-Ketryx-project-settings"
last_reviewed: 2026-06-11
---

# How can I use "Release ref pattern" for connected repositories in the Ketryx project settings?

> **In short:** Versioning items can be important when using Ketryx. Point-wise items will only appear in the version they are marked with, and long-lived items will appear in all versions from their introduction to their obsolescence (more on that here).

Versioning items can be important when using Ketryx. Point-wise items will only appear in the version they are marked with, and long-lived items will appear in all versions from their introduction to their obsolescence (more on that [here](what-are-long-lived-and-point-wise-short-lived-configuration-items-what-are-the.md)). When you want to appropriately version items from connected repositories, like dependencies or Git-based configuration items, you should set Release ref pattern to ensure Ketryx can infer a version number from branches or tags in the repository and match that with a project release version number in Ketryx.

After doing this, Ketryx will know which dependencies and/or Git-based configuration items appear in each release version of the project.

When setting up the Release ref pattern, you should use # as a SemVer-compatible version placeholder. For example, release/# will match release/3.2.1, release/3.2, or release/3, as version numbers 3.2.1, 3.2.0, and 3.0.0, respectively.

## Related articles

- [How can I use \"Analyzed branch or tag\" for connected repositories in the Ketryx project settings?](how-can-i-use-analyzed-branch-or-tag-for-connected-repositories-in-the-ketryx.md)
- [How do we get documentation to reflect git-based configuration items?](how-do-we-get-documentation-to-reflect-git-based-configuration-items.md)
- [How do you add your repository to Ketryx for an existing project?](how-do-you-add-your-repository-to-ketryx-for-an-existing-project.md)
- [How do you add your repository to Ketryx for a new project?](how-do-you-add-your-repository-to-ketryx-for-a-new-project.md)
- [Is it possible to manage branched requirements in Ketryx?](is-it-possible-to-manage-branched-requirements-in-ketryx.md)