Vale 3

.github/workflows/pull_request.yaml

@@ -7,13 +7,13 @@ on:
 
 jobs:
   qa:
-    uses: stakater/.github/.github/workflows/[email protected].62
+    uses: stakater/.github/.github/workflows/[email protected].64
     with:
       MD_CONFIG: .github/md_config.json
       DOC_SRC: content
       MD_LINT_CONFIG: .markdownlint.yaml
   build:
-    uses: stakater/.github/.github/workflows/[email protected].62
+    uses: stakater/.github/.github/workflows/[email protected].64
     with:
       DOCKER_FILE_PATH: Dockerfile
     secrets:

.github/workflows/push.yaml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   push:
-    uses: stakater/.github/.github/workflows/[email protected].62
+    uses: stakater/.github/.github/workflows/[email protected].64
     with:
       DOCKER_FILE_PATH: Dockerfile
       RELEASE_BRANCH: main

.github/workflows/release.yaml

@@ -7,6 +7,6 @@ on:
 
 jobs:
   release:
-    uses: stakater/.github/.github/workflows/[email protected].62
+    uses: stakater/.github/.github/workflows/[email protected].64
     secrets:
       SLACK_WEBHOOK_URL: ${{ secrets.STAKATER_DELIVERY_SLACK_WEBHOOK }}

.gitignore

@@ -20,3 +20,4 @@ node_modules
 
 # Build files
 site/
+styles/

.vale.ini

@@ -1,7 +1,8 @@
-StylesPath = "vocabulary/styles"
+StylesPath = styles
 MinAlertLevel = warning
 
-Vocab = "Stakater"
+Packages = https://github.com/stakater/vale-package/releases/download/v0.0.3/Stakater.zip
+Vocab = Stakater
 
 # Only check MarkDown files
 [*.md]

content/sealed-secrets.md

@@ -48,8 +48,8 @@ Lets create a sample k8s secret that will be used for MySQL:
 
     where:
 
-    * `SECRET_FILE`: the name of the yaml file containing the k8s secret
-    * `SEALED_SECRET`: the name of the yaml file that will contain the sealed secret
+    * `SECRET_FILE`: the name of the YAML file containing the k8s secret
+    * `SEALED_SECRET`: the name of the YAML file that will contain the sealed secret
 
 1. Add and commit this sealed secret to source control
 

content/vault.md

@@ -76,7 +76,7 @@ To use the Vault CLI, a token is required. Users can get/renew/revoke a token fr
 
 1. Once a token is fetched, users can use the terminal provided by the UI, so there is no need to install the Vault CLI:
 
-    ![Vault-cli](./images/vault_cli.png)
+    ![Vault-CLI](./images/vault_cli.png)
 
 1. If using the Vault CLI, login with the token:
 

renovate.json

@@ -1,6 +1,21 @@
 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
   "extends": [
-    "config:base"
+    "config:recommended"
+  ],
+  "labels": [
+    "dependencies"
+  ],
+  "customManagers": [
+    {
+        "customType": "regex",
+        "fileMatch": [
+            ".vale.ini"
+        ],
+        "matchStrings": [
+            "https:\/\/github.com\/(?<depName>.*)\/releases\/download\/(?<currentValue>.*)\/.*.tar.gz"
+        ],
+        "datasourceTemplate": "github-release-attachments"
+    }
   ]
 }