chore: node 20 gh

.github/workflows/test.yml

@@ -6,12 +6,12 @@ jobs:
   build-and-test:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-node@v2
+      - uses: actions/checkout
+      - uses: actions/setup-node
         with:
           node-version: '20'
       - name: Cache Node.js modules
-        uses: actions/cache@v2
+        uses: actions/cache
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}

README.md

@@ -93,12 +93,8 @@ The Deployment Frequency chart plots the average deployment frequency using a lo
 
 ### Change Fail Percentage
 
-Coming Soon
-
 ### Mean Time to Restore (MTTR)
 
-Coming Soon
-
 ### Other Considerations for Stability Metrics
 
 The one murky area remaining related to stability is the release or situation that causes degraded stability for end-users but is fixed either by a new release or a configuration change. For example, the Redis AddOn runs out of space or connections and users are unable to log in until the service configuration has been manually updated. This ties into the Availability metric referenced in the 2019 version of the DevOps Report. Ideally, it would also add to MTTR metric.