🔖 bump to v2.1.3

README.md

@@ -29,7 +29,7 @@ This action enables you to get the PR no matter which event type triggered the w
 
 ```yml
     steps:
-      - uses: 8BitJonny/[email protected].2
+      - uses: 8BitJonny/[email protected].3
         id: PR
 
       - run: echo "Your PR number is ${{ steps.PR.outputs.number }} and its JSON is ${{ steps.PR.outputs.pr }}"
@@ -39,7 +39,7 @@ This action enables you to get the PR no matter which event type triggered the w
 See [action.yml](action.yml) for more details.
 ```yml
     steps:
-      - uses: 8BitJonny/[email protected].2
+      - uses: 8BitJonny/[email protected].3
         id: PR
         with:
           # Authetication token to access GitHub APIs. (Can be omitted by default.)
@@ -56,7 +56,7 @@ See [action.yml](action.yml) for more details.
 See [action.yml](action.yml) for more details.
 ```yml
     steps:
-      - uses: 8BitJonny/[email protected].2
+      - uses: 8BitJonny/[email protected].3
         id: PR
 
       - run: echo "PR ${prNumber} ${prTitle} at ${prUrl} is ${prJSON}"
@@ -81,7 +81,7 @@ Useful when the information you're looking for is not exported as a direct outpu
 See [GitHub Documentation](https://docs.github.com/en/rest/commits/commits#list-pull-requests-associated-with-a-commit) for details how the object looks like.
 ```yml
     steps:
-      - uses: 8BitJonny/[email protected].2
+      - uses: 8BitJonny/[email protected].3
         id: PR
 
       - name: "Pull Request ${{ steps.PR.outputs.number }}"
@@ -100,7 +100,7 @@ A short form of the article's explanation is, that Github creates an extra merge
 To always find and pass the correct commit SHA to this action use this workflow config:
 ```yml
     steps:
-      - uses: 8BitJonny/[email protected].2
+      - uses: 8BitJonny/[email protected].3
         id: PR
         with:
           sha: ${{ github.event.pull_request.head.sha }}