Skip to content

Commit

Permalink
postrelease: automatically update the Go version
Browse files Browse the repository at this point in the history
Extract the Go version from go.mod and use it when we update the
version numbers used throughout the docs.

This has several advantages:
1. We no longer need to remember to periodically update this variable.
   For example, Teleport 17 was built with Go 1.23 but the docs still
   (incorrectly) mention Go 1.22.
2. We get even more precision, as we'll start using the full patch
   version of Go instead of only the minor.
  • Loading branch information
zmb3 committed Dec 3, 2024
1 parent d20c267 commit 44da1a1
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions .github/workflows/post-release.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -94,12 +94,17 @@ jobs:
git config --global user.email "[email protected]"
git config --global user.name "GitHub"
# get Go version from go.mod
GO_VERSION=$(go mod edit -json | jq -r .Go)
# update versions in docs/config.json
# for docker images replace version number after <docker image name>:
jq --arg major "${MAJOR_VERSION}" \
--arg version "${FULL_VERSION}" \
--arg go_version "${GO_VERSION}" \
'.variables.teleport.major_version |= $major |
.variables.teleport.version |= $version |
.variables.teleport.golang |= $go_version |
.variables.teleport.plugin.version |= $version |
.variables.teleport.latest_oss_docker_image |= sub(":.*";":")+$version |
.variables.teleport.latest_oss_debug_docker_image |= sub(":.*";":")+$version |
Expand Down

0 comments on commit 44da1a1

Please sign in to comment.