# Is the 'latest' version of cmake-docs deployed from the 'release' branch?
**URL:** https://discourse.cmake.org/t/is-the-latest-version-of-cmake-docs-deployed-from-the-release-branch/10371
**Category:** Development
**Created:** [March 15, 2024, 3:38am UTC](https://discourse.cmake.org/t/is-the-latest-version-of-cmake-docs-deployed-from-the-release-branch/10371 "2024-03-15T03:38:35Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@hwhsu1231](https://discourse.cmake.org/u/hwhsu1231)
#### Post date: [March 15, 2024, 3:38am UTC](https://discourse.cmake.org/t/is-the-latest-version-of-cmake-docs-deployed-from-the-release-branch/10371/1 "2024-03-15T03:38:35Z")
Hello, CMake Team.
According to the cmake-docs, we can see that the [‘latest’](https://cmake.org/cmake/help/latest/index.html) version corresponds to the latest release (e.g. `3.28.5`) or relase candidate (e.g. `3.29.0-rc1`).
I wonder:
1. Whether the ‘latest’ version of cmake-docs is deployed from the [‘release’](https://github.com/Kitware/CMake/tree/release) branch?
2. Or it is deployed from the latest [tag](https://github.com/Kitware/CMake/tags) acquired through a set of internal design logic calculations?
In other words, is the ‘release’ branch designed for the ‘latest’ version of cmake-docs? (Because I noticed that the HEAD of the ‘release’ branch is usually at the commit with a tag)
```bash
(.venv) hwhsu1231@vb-kubuntu:~/Repo/testing/CMake$ git status
On branch release
nothing to commit, working tree clean
(.venv) hwhsu1231@vb-kubuntu:~/Repo/testing/CMake$ git log --oneline
788c204788 (HEAD -> release, tag: v3.29.0-rc4, relase) CMake 3.29.0-rc4
e497fbfca3 Merge topic 'Apple-TBD-in-subdirecory' into release-3.29
3e90c88733 Merge branch 'release-3.28' into release-3.29
742af6cff7 Merge topic 'autogen-makefile-depfile' into release-3.29
8ebdee9314 Merge topic 'autogen-makefile-depfile' into release-3.28
8f0801cacc Merge topic 'LINKER_TYPE-mold-support' into release-3.29
d93a7c18d8 Merge topic 'fc-MakeAvailable-leak-var' into release-3.29
bcc26ce465 Apple Text Based Stubs: should be usage in subdirectories
```
---
### Author:  [@craig.scott](https://discourse.cmake.org/u/craig.scott)
#### Post date: [March 16, 2024, 12:35am UTC](https://discourse.cmake.org/t/is-the-latest-version-of-cmake-docs-deployed-from-the-release-branch/10371/2 "2024-03-16T00:35:23Z")
As far as I’m aware, we only update the published docs when there’s a tagged release, but @brad.king can provide a more authoritative answer.
---
### Author:  [@brad.king](https://discourse.cmake.org/u/brad.king)
#### Post date: [March 18, 2024, 1:53pm UTC](https://discourse.cmake.org/t/is-the-latest-version-of-cmake-docs-deployed-from-the-release-branch/10371/3 "2024-03-18T13:53:57Z")
The `/latest` docs correspond to the highest-numbered tag created from the `release` branch. It is deployed by the CI pipeline used to create the release binaries.
---
### Author:  [@hwhsu1231](https://discourse.cmake.org/u/hwhsu1231)
#### Post date: [March 19, 2024, 7:16am UTC](https://discourse.cmake.org/t/is-the-latest-version-of-cmake-docs-deployed-from-the-release-branch/10371/4 "2024-03-19T07:16:55Z")
But we can acquire the highest-numbered tag from the `master` branch as well, right?
From the following screentshot, I noticed that the `release` branch doesn’t always correspond to the highest-numbered tag. Therefore, we cannot acquire the status of the highest-numbered tag by simply using the following command, right?
```auto
git clone --depth=1 --branch=release https://github.com/Kitware/CMake.git
```
---
### Author:  [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [March 29, 2024, 12:02pm UTC](https://discourse.cmake.org/t/is-the-latest-version-of-cmake-docs-deployed-from-the-release-branch/10371/5 "2024-03-29T12:02:18Z")
> [@hwhsu1231](#):
>
> From the following screentshot, I noticed that the `release` branch doesn’t always correspond to the highest-numbered tag. Therefore, we cannot acquire the status of the highest-numbered tag by simply using the following command, right?
No, this would get anything headed towards the next patch release. I don’t think you can get it through `git clone` like that. Instead, maybe do an API query for tags against GitLab or Github (whichever is easier for you) and clone the highest in that list with `--depth 1`?