Update the README.md file for v3.

README.md

@@ -1,4 +1,4 @@
-# setup-bazelisk v2
+# setup-bazelisk v3
 Set up your GitHub Actions workflow with a specific version of Bazelisk
 
 Note that GitHub Actions includes Bazelisk by default as of <https://github.com/actions/virtual-environments/pull/490> so this setup is not necessary unless you want to customize the Bazelisk version, or are running Bazel inside a container.
@@ -12,8 +12,8 @@ This action sets up Bazelisk for use in actions by:
 
 # What's new
 
-- Updated to the node16 runtime by default
-  - This requires a minimum [Actions Runner](https://github.com/actions/runner/releases/tag/v2.285.0) version of v2.285.0 to run, which is by default available in GHES 3.4 or later.
+- Updated to the node20 runtime by default
+  - This requires a minimum [Actions Runner](https://github.com/actions/runner/releases/tag/v2.308.0) version of v2.308.0 to run.
 
 # Usage
 
@@ -22,10 +22,10 @@ See [action.yml](action.yml)
 Basic:
 ```yaml
 steps:
-- uses: actions/checkout@v3
-- uses: bazelbuild/setup-bazelisk@v2
+- uses: actions/checkout@v4
+- uses: bazelbuild/setup-bazelisk@v3
 - name: Mount bazel cache  # Optional
-  uses: actions/cache@v3
+  uses: actions/cache@v4
   with:
     path: "~/.cache/bazel"
     key: bazel
@@ -34,7 +34,7 @@ steps:
 
 # Known issues on Windows
 * This action doesn't work with PowerShell. Make sure to have `shell: bash` in you `run:` steps. ([#3](https://github.com/bazelbuild/setup-bazelisk/issues/3))
-* Windows removes one of the slashes (`/`) when two are present (`bazel test //tests/...` becomes `bazel test /tests/...` and fails). ([#4](https://github.com/bazelbuild/setup-bazelisk/issues/4))  
+* Windows removes one of the slashes (`/`) when two are present (`bazel test //tests/...` becomes `bazel test /tests/...` and fails). ([#4](https://github.com/bazelbuild/setup-bazelisk/issues/4))
   As a workaround, don't have any prefix `//`. Since all runs start at WORKSPACE dir, it should work all the same.
 
 Full workaround example on windows: