Skip to content

Commit e1dca7c

Browse files
committed
Bump docs to mention v2
1 parent e2dda67 commit e1dca7c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -21,20 +21,20 @@
2121
To run the action with the latest swift version available, simply add the action as a step in your workflow:
2222

2323
```yaml
24-
- uses: swift-actions/setup-swift@v1
24+
- uses: swift-actions/setup-swift@v2
2525
```
2626
2727
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:
2828
```yaml
29-
- uses: swift-actions/setup-swift@v1
29+
- uses: swift-actions/setup-swift@v2
3030
- name: Get swift version
3131
run: swift --version # Swift 5.10
3232
```
3333

3434
A specific Swift version can be set using the `swift-version` input:
3535

3636
```yaml
37-
- uses: swift-actions/setup-swift@v1
37+
- uses: swift-actions/setup-swift@v2
3838
with:
3939
swift-version: "5.1.0"
4040
- name: Get swift version
@@ -51,7 +51,7 @@ strategy:
5151
os: [ubuntu-latest, macos-latest]
5252
swift: ["5.4.3", "5.2.4"]
5353
steps:
54-
- uses: swift-actions/setup-swift@v1
54+
- uses: swift-actions/setup-swift@v2
5555
with:
5656
swift-version: ${{ matrix.swift }}
5757
- name: Get swift version
@@ -75,22 +75,22 @@ In other words specifying...
7575
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:
7676

7777
```
78-
- uses: swift-actions/setup-swift@v1
78+
- uses: swift-actions/setup-swift@v2
7979
with:
8080
swift-version: '5.0'
8181
```
8282

8383
Not:
8484

8585
```
86-
- uses: swift-actions/setup-swift@v1
86+
- uses: swift-actions/setup-swift@v2
8787
with:
8888
swift-version: 5.0
8989
```
9090

9191
## Keeping the action up-to-date
9292

93-
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`).
93+
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`).
9494

9595
### Specific version
9696

0 commit comments

Comments
 (0)