Skip to content

Commit 081fb72

Browse files
authored
DOCS: Release process needs tip on how to find latest version (#4007)
<!-- ## Before submiting a pull request Please make sure you've run the following commands from the root directory. bin/generate-all.sh (this runs commands like "go generate", fixes formatting, and so on) ## Release changelog section Help keep the release changelog clear by pre-naming the proper section in the GitHub pull request title. Some examples: * CICD: Add required GHA permissions for goreleaser * DOCS: Fixed providers with "contributor support" table * ROUTE53: Allow R53_ALIAS records to enable target health evaluation More examples/context can be found in the file .goreleaser.yml under the 'build' > 'changelog' key. !-->
1 parent ae9759d commit 081fb72

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

documentation/release/release-engineering.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,10 @@ git commit -am "CHORE: generate-all.sh"
3232
## Step 2. Tag the commit in main that you want to release
3333

3434
```shell
35+
git tag -l |grep -F v4. | sort --version-sort --field-separator=. --key=2,2 | tail
3536
export VERSION=v4.x.0
3637
git checkout main
38+
git pull --rebase --ff-only --prune
3739
git tag -m "Release $VERSION" -a $VERSION
3840
git push origin HEAD --tags
3941
```

0 commit comments

Comments
 (0)