bump go version

frantjc · Jan 4, 2025 · ca5df1b · ca5df1b
1 parent f32a3f3
commit ca5df1b
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/.github/workflows/build-shims.yml b/.github/workflows/build-shims.yml
@@ -10,7 +10,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.22
+          go-version: 1.23
       - uses: crazy-max/ghaction-upx@v3
         with:
           install-only: true

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -17,7 +17,7 @@ jobs:
           node-version: 20
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.22
+          go-version: 1.23
       - uses: golangci/[email protected]
       - run: make download
       - run: make test

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -14,7 +14,7 @@ jobs:
           fetch-depth: 0
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.22
+          go-version: 1.23
           cache: true
       - uses: crazy-max/ghaction-upx@v3
         with:

diff --git a/docs/github-actions.md b/docs/github-actions.md
@@ -16,13 +16,13 @@ jobs:
     steps:
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.22
+          go-version: 1.23
 ```
 
 Rather, it is intended to run an Action from within a workflow, like so:
 
 ```sh
-forge use actions/setup-go@v5 --with go-version=1.22
+forge use actions/setup-go@v5 --with go-version=1.23
 ```
 
 When running an Action, Forge mounts the current working directory to the Action's `GITHUB_WORKSPACE` as well as directories respecting the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) to the Action's `RUNNER_TOOLCACHE` and `RUNNER_TEMP`. So, after the above command is ran, if it succeeds, `go` should be installed somewhere in `XDG_CACHE_HOME/forge/runner/toolcache`. This can be found more easily by running: