IBM · Jan 24, 2025 · Jan 24, 2025 · Jan 24, 2025 · Jan 24, 2025 · Jan 24, 2025
diff --git a/.eslintrc.js b/.eslintrc.js
@@ -15,6 +15,7 @@ module.exports = {
       {
         singleQuote: true,
         arrowParens: 'avoid',
+        trailingComma: 'es5',
       },
     ],
     'no-console': 0,

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -11,7 +11,7 @@ Please make sure that your PR fulfills the following requirements:
 - [ ] Docs have been added / updated (for bug fixes / features)
 - [ ] Dependencies have been updated as needed
 - [ ] `.secrets.baseline` has been updated as needed
-- [ ] `npm run generate-utilities-docs` has been run if any files in `packages/utilities/src` have been updated
+- [ ] `npm run update-utilities` has been run if any files in `packages/utilities/src` have been updated
 
 #### Checklist for adding a new validation rule:
 - [ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)

diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
@@ -3,7 +3,7 @@
 # semantic-release is also run to create a new release (if
 # warranted by the new commits being built).
 
-name: Build/Test/Publish
+name: build
 
 on: 
   push:
@@ -16,7 +16,7 @@ on:
 jobs:
   detect-secrets:
     if: "!contains(github.event.head_commit.message, '[skip ci]')"
-    name: Detect-Secrets
+    name: detect-secrets
     runs-on: ubuntu-latest
     strategy:
       matrix:
@@ -46,8 +46,8 @@ jobs:
           detect-secrets -v audit --report --fail-on-unaudited --fail-on-live --fail-on-audited-real .secrets.baseline
 
   build:
+    name: build-test (node v${{ matrix.node-version }})
     needs: detect-secrets
-    name: Build/Test (Node v${{ matrix.node-version }})
     runs-on: ubuntu-latest
     strategy:
       matrix:
@@ -73,7 +73,7 @@ jobs:
 
   publish-release:
     needs: build
-    name: Semantic-Release
+    name: semantic-release
     if: "github.ref_name == 'main' && github.event_name != 'pull_request'"
     runs-on: ubuntu-latest
 

diff --git a/.github/workflows/docker.yaml b/.github/workflows/docker.yaml
@@ -3,20 +3,31 @@
 # job is separated from the publishing job, as it may fail independently and
 # we need to be able to retry it without re-running the publish step.
 
-name: Docker Deploy
+name: docker
 
 on:
   release:
-    types: [created]
+    types:
+      - published
   workflow_dispatch:
     # Allow this workflow to be triggered manually
 
 jobs:
-  deploy-docker-image:
-    name: Deploy image
+  deploy-image:
+    # We want to trigger this job ONLY for a published release
+    # related to the "ibm-openapi-validator" package.
+    name: deploy-image
+    if: "contains(github.ref_name, 'ibm-openapi-validator')"
     runs-on: ubuntu-latest
 
     steps:
+      # Display some info about the build for debugging purposes.
+      - name: Trigger info
+        run: |
+          echo "Build triggered by event: " ${{ github.event_name }}
+          echo "                 git ref: " ${{ github.ref }}
+          echo "            git ref_name: " ${{ github.ref_name }}
+
       - name: Checkout repository
         uses: actions/checkout@v4
 

diff --git a/.releaserc b/.releaserc
@@ -1,25 +1,12 @@
 {
-  "branches": "main",
+  "branches": ["main"],
   "debug": true,
   "plugins": [
     "@semantic-release/commit-analyzer",
     "@semantic-release/release-notes-generator",
     "@semantic-release/changelog",
     "@semantic-release/npm",
     "@semantic-release/git",
-    [
-      "@semantic-release/exec",
-      {
-        "publishCmd": "npm run pkg"
-      }
-    ],
-    [
-      "@semantic-release/github",
-      {
-        "assets": [
-          "bin/*"
-        ]
-      }
-    ]
+    "@semantic-release/github"
   ]
 }
diff --git a/.secrets.baseline b/.secrets.baseline
@@ -3,7 +3,7 @@
     "files": "package-lock.json|^.secrets.baseline$",
     "lines": null
   },
-  "generated_at": "2025-01-09T19:49:59Z",
+  "generated_at": "2025-03-06T22:00:57Z",
   "plugins_used": [
     {
       "name": "AWSKeyDetector"
@@ -106,7 +106,7 @@
       }
     ]
   },
-  "version": "0.13.1+ibm.56.dss",
+  "version": "0.13.1+ibm.62.dss",
   "word_list": {
     "file": null,
     "hash": null

diff --git a/docs/automated-quality-screening.md b/docs/automated-quality-screening.md
@@ -1,6 +1,6 @@
-# Automated Qualitative Screening
+# Automated Quality Screening
 
-The validator provides Automated Qualitative Screening (AQS) scores via the `-q` (or
+The validator provides Automated Quality Screening (AQS) scores via the `-q` (or
 `--impact-score`) flag. These scores help you evaluate risk and make decisions about investing in
 the quality of your service's API. AQS scores are not a substitute for expert review, but minimum
 AQS scores may be a prerequisite to a review.