Release v2.6.0 (#207)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -30,7 +30,7 @@ Steps to reproduce the issue:
 
 **Action version:**
 
-- Version: **microsoft/ps-rule@v2.5.2**
+- Version: **microsoft/ps-rule@v2.6.0**
 
 **Additional context**
 

.github/workflows/analyze.yaml

@@ -29,7 +29,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Run PSRule analysis
-        uses: microsoft/ps-rule@v2.5.2
+        uses: microsoft/ps-rule@main
         with:
           modules: PSRule.Rules.MSFT.OSS
           prerelease: true

README.md

@@ -14,7 +14,7 @@ To get the latest stable release use:
 
 ```yaml
 - name: Run PSRule analysis
-  uses: microsoft/ps-rule@v2.5.2
+  uses: microsoft/ps-rule@v2.6.0
 ```
 
 To get the latest bits use:
@@ -29,7 +29,7 @@ For example:
 
 ```yaml
 - name: Run PSRule analysis
-  uses: microsoft/ps-rule@v2.5.2
+  uses: microsoft/ps-rule@v2.6.0
   with:
     version: '1.11.1'
 ```
@@ -185,8 +185,8 @@ When set:
 
 To use PSRule:
 
-1. See [Creating a workflow file](https://help.github.com/en/articles/configuring-a-workflow#creating-a-workflow-file).
-2. Reference `microsoft/ps-rule@v2.5.2`.
+1. See [Creating a workflow file](https://help.github.com/articles/configuring-a-workflow#creating-a-workflow-file).
+2. Reference `microsoft/ps-rule@v2.6.0`.
 For example:
 
 ```yaml
@@ -202,7 +202,7 @@ jobs:
       uses: actions/checkout@v3
 
     - name: Run PSRule analysis
-      uses: microsoft/ps-rule@v2.5.2
+      uses: microsoft/ps-rule@v2.6.0
 ```
 
 3. Create rules within the `.ps-rule/` directory.

docs/CHANGELOG-v2.md

@@ -6,6 +6,8 @@ See [upgrade notes][upgrade-notes] for helpful information when upgrading from p
 
 ## Unreleased
 
+## v2.6.0
+
 What's changed since v2.5.2:
 
 - Engineering: