diff --git a/README.md b/README.md
index f9f19444..ea8a4798 100644
--- a/README.md
+++ b/README.md
@@ -21,12 +21,12 @@
 To run the action with the latest swift version available, simply add the action as a step in your workflow:
 
 ```yaml
-- uses: swift-actions/setup-swift@v1
+- uses: swift-actions/setup-swift@v2
 ```
 
 After the environment is configured you can run swift commands using the standard [`run`](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsrun) step:
 ```yaml
-- uses: swift-actions/setup-swift@v1
+- uses: swift-actions/setup-swift@v2
 - name: Get swift version
   run: swift --version # Swift 5.10
 ```
@@ -34,7 +34,7 @@ After the environment is configured you can run swift commands using the standar
 A specific Swift version can be set using the `swift-version` input:
 
 ```yaml
-- uses: swift-actions/setup-swift@v1
+- uses: swift-actions/setup-swift@v2
   with:
     swift-version: "5.1.0"
 - name: Get swift version
@@ -51,7 +51,7 @@ strategy:
     os: [ubuntu-latest, macos-latest]
     swift: ["5.4.3", "5.2.4"]
 steps:
-- uses: swift-actions/setup-swift@v1
+- uses: swift-actions/setup-swift@v2
   with:
     swift-version: ${{ matrix.swift }}
 - name: Get swift version
@@ -75,7 +75,7 @@ In other words specifying...
 YAML interprets eg. `5.0` as a float, this action will then interpret that as `5` which will result in eg. Swift 5.5 being resolved. Quote your inputs! Thus:
 
 ```
-- uses: swift-actions/setup-swift@v1
+- uses: swift-actions/setup-swift@v2
   with:
     swift-version: '5.0'
 ```
@@ -83,14 +83,14 @@ YAML interprets eg. `5.0` as a float, this action will then interpret that as `5
 Not:
 
 ```
-- uses: swift-actions/setup-swift@v1
+- uses: swift-actions/setup-swift@v2
   with:
     swift-version: 5.0
 ```
 
 ## Keeping the action up-to-date
 
-You have two options for keeping this action up-to-date: either you define a specific version (like `v1.17.0`) or use the major version tag (like `v1`).
+You have two options for keeping this action up-to-date: either you define a specific version (like `v2.0.1`) or use the major version tag (like `v2`).
 
 ### Specific version