bump version in readme from v1->v3

README.md

@@ -48,7 +48,7 @@ don't allow this because they don't work on a level of individual jobs or steps.
 ## Example
 
 ```yaml
-- uses: step-security/paths-filter@v2
+- uses: step-security/paths-filter@v3
   id: changes
   with:
     filters: |
@@ -75,7 +75,7 @@ For more scenarios see [examples](#examples) section.
 ## Usage
 
 ```yaml
-- uses: step-security/paths-filter@v1
+- uses: step-security/paths-filter@v3
   with:
     # Defines filters applied to detected changed files.
     # Each filter has a name and a list of rules.
@@ -168,7 +168,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v3
-    - uses: step-security/paths-filter@v1
+    - uses: step-security/paths-filter@v3
       id: filter
       with:
         filters: |
@@ -212,7 +212,7 @@ jobs:
       frontend: ${{ steps.filter.outputs.frontend }}
     steps:
     # For pull requests it's not necessary to checkout the code
-    - uses: step-security/paths-filter@v1
+    - uses: step-security/paths-filter@v3
       id: filter
       with:
         filters: |
@@ -258,7 +258,7 @@ jobs:
       packages: ${{ steps.filter.outputs.changes }}
     steps:
     # For pull requests it's not necessary to checkout the code
-    - uses: step-security/paths-filter@v1
+    - uses: step-security/paths-filter@v3
       id: filter
       with:
         filters: |
@@ -300,7 +300,7 @@ jobs:
       pull-requests: read
     steps:
     - uses: actions/checkout@v3
-    - uses: step-security/paths-filter@v1
+    - uses: step-security/paths-filter@v3
       id: filter
       with:
         filters: ... # Configure your filters
@@ -325,7 +325,7 @@ jobs:
         # This may save additional git fetch roundtrip if
         # merge-base is found within latest 20 commits
         fetch-depth: 20
-    - uses: step-security/paths-filter@v1
+    - uses: step-security/paths-filter@v3
       id: filter
       with:
         base: develop # Change detection against merge-base with this branch
@@ -349,7 +349,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v3
-    - uses: step-security/paths-filter@v1
+    - uses: step-security/paths-filter@v3
       id: filter
       with:
         # Use context to get the branch where commits were pushed.
@@ -383,7 +383,7 @@ jobs:
 
       # Filter to detect which files were modified
       # Changes could be, for example, automatically committed
-    - uses: step-security/paths-filter@v1
+    - uses: step-security/paths-filter@v3
       id: filter
       with:
         base: HEAD
@@ -398,7 +398,7 @@ jobs:
   <summary>Define filter rules in own file</summary>
 
 ```yaml
-- uses: step-security/paths-filter@v1
+- uses: step-security/paths-filter@v3
       id: filter
       with:
         # Path to file where filters are defined
@@ -411,7 +411,7 @@ jobs:
   <summary>Use YAML anchors to reuse path expression(s) inside another rule</summary>
 
 ```yaml
-- uses: step-security/paths-filter@v1
+- uses: step-security/paths-filter@v3
       id: filter
       with:
         # &shared is YAML anchor,
@@ -432,7 +432,7 @@ jobs:
   <summary>Consider if file was added, modified or deleted</summary>
 
 ```yaml
-- uses: step-security/paths-filter@v1
+- uses: step-security/paths-filter@v3
       id: filter
       with:
         # Changed file can be 'added', 'modified', or 'deleted'.
@@ -460,7 +460,7 @@ jobs:
   <summary>Passing list of modified files as command line args in Linux shell</summary>
 
 ```yaml
-- uses: step-security/paths-filter@v1
+- uses: step-security/paths-filter@v3
   id: filter
   with:
     # Enable listing of files matching each filter.
@@ -486,7 +486,7 @@ jobs:
   <summary>Passing list of modified files as JSON array to another action</summary>
 
 ```yaml
-- uses: step-security/paths-filter@v1
+- uses: step-security/paths-filter@v3
   id: filter
   with:
     # Enable listing of files matching each filter.