# Frequently Asked Questions

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

Carlton

- Updated 1 year ago

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](https://support.ketryx.com/hc/en-us/articles/23226084383501-What-are-long-lived-and-point-wise-short-lived-configuration-items-What-are-the-differences-between-the-two)). 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.

### Previous article

[How is our connected source code repository processed by Ketryx?](https://support.ketryx.com/hc/en-us/articles/31173445927821-How-is-our-connected-source-code-repository-processed-by-Ketryx)

### Next article

[How can I use "Analyzed branch or tag" for connected repositories in the Ketryx project settings?](https://support.ketryx.com/hc/en-us/articles/30924834051469-How-can-I-use-Analyzed-branch-or-tag-for-connected-repositories-in-the-Ketryx-project-settings)