Skip to content

Commit 75ca28d

Browse files
committed
README: Should always use a release version branch
From 3.12 onward, there is no 3.12 version branch but only release branches 3.12.0 etc., but for 3.10 and 3.11, we should also use the release branch to avoid discrepancies between the release build and the version branch HEAD
1 parent fb2dd95 commit 75ca28d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

CIRCLECI.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ steps below.
172172
| string | `workflow` | `release` |
173173
| string | `release-type` | `arangodb` |
174174
| string | `docs-version` | `3.11` (the docs version folder) |
175-
| string | `arangodb-branch` | `3.11` (the arangodb/arangodb branch to compile) |
175+
| string | `arangodb-branch` | `3.11.4` (the arangodb/arangodb branch to compile) |
176176
| string | `arangodb-version` | `3.11.4` (updates the `versions.yaml` file) |
177177

178178
The ArangoDB release workflow includes the following jobs:

0 commit comments

Comments
 (0)