deps: update dependency autoprefixer to v10.4.15 (#1909)

Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com> Co-authored-by: odubajDT <ondrej.dubaj@dynatrace.com>
keptn · Sep 4, 2023 · 8dbec2d · 8dbec2d
1 parent 6ce03d6
commit 8dbec2d
Show file tree

Hide file tree

Showing 6 changed files with 48 additions and 35 deletions.
diff --git a/docs/content/en/docs/getting-started/_index.md b/docs/content/en/docs/getting-started/_index.md
@@ -10,7 +10,7 @@ The following is an imperative walkthrough.
 
 ## Prerequisites
 
-- [Docker](https://docker.com)
+- [Docker](https://docs.docker.com/get-started/overview/)
 - [kubectl](https://kubernetes.io/docs/reference/kubectl/)
 - A Kubernetes cluster >= 1.24 (we recommend [Kubernetes kind](https://kind.sigs.k8s.io/docs/user/quick-start/))
   (`kind create cluster`)

diff --git a/docs/content/en/docs/intro-klt/usecase-orchestrate.md b/docs/content/en/docs/intro-klt/usecase-orchestrate.md
@@ -50,9 +50,10 @@ example.
 
 The steps to implement pre- and post-deployment orchestration are:
 
-1. [Define evaluations to be performed pre- and post-deployment](#define-evaluations-to-be-performed-pre--and-post-deployment)
-1. [Define tasks to be performed pre- and post-deployment](#define-tasks-to-be-performed-pre--and-post-deployment)
-1. [Integrate evaluations and tasks into the cluster](#integrate-evaluations-and-tasks-into-the-cluster)
+* [Using this exercise](#using-this-exercise)
+* [Define evaluations to be performed pre- and post-deployment](#define-evaluations-to-be-performed-pre--and-post-deployment)
+* [Define tasks to be performed pre- and post-deployment](#define-tasks-to-be-performed-pre--and-post-deployment)
+* [Integrate evaluations and tasks into the cluster](#integrate-evaluations-and-tasks-into-the-cluster)
 
 This is the third of three exercises in the
 [Introducing the Keptn Lifecycle Toolkit](_index.md)
@@ -148,7 +149,7 @@ spec:
 For more information about sending Slack notifications with KLT, see
 [Implement Slack notifications](../implementing/slack.md).
 The code to be executed is expressed as a
-[Deno](https://deno.land/)
+[Deno](https://deno.com)
 script, which uses JavaScript syntax.
 It can be embedded in the definition file
 or pulled in from a remote webserver that is specified.

diff --git a/docs/content/en/docs/yaml-crd-ref/taskdefinition.md b/docs/content/en/docs/yaml-crd-ref/taskdefinition.md
@@ -122,7 +122,7 @@ When using the `deno-runtime` runner to define a task,
 the task is coded in Deno-script
 (which is mostly the same as JavaScript and TypeScript)
 and executed in the
-[Deno](https://deno.land/manual) runner,
+[Deno](https://deno.com/manual) runner,
 which is a lightweight runtime environment
 that executes in your namespace.
 Note that Deno has tighter restrictions
@@ -149,7 +149,7 @@ spec:
 
 * **spec**
   * **deno** -- Specify that the task uses the `deno-runtime`
-    and is expressed as a [Deno](https://deno.land/) script.
+    and is expressed as a [Deno](https://deno.com/) script.
     Refer to [deno runtime](https://github.com/keptn/lifecycle-toolkit/tree/main/runtimes/deno-runtime)
     for more information about this runner.
 

diff --git a/docs/package-lock.json b/docs/package-lock.json
diff --git a/docs/package.json b/docs/package.json
@@ -1,6 +1,6 @@
 {
     "dependencies": {
-        "autoprefixer": "^10.4.13",
+        "autoprefixer": "^10.4.15",
         "postcss-cli": "^10.1.0"
     }
 }
diff --git a/runtimes/deno-runtime/README.md b/runtimes/deno-runtime/README.md
@@ -8,7 +8,7 @@ docker build -t keptnsandbox/klc-runtime:${VERSION} .
 
 ## Usage
 
-The Keptn deno runtime uses [Deno](https://deno.land/)
+The Keptn deno runtime uses [Deno](https://deno.com/)
 to execute Javascript/Typescript code.
 The Keptn Lifecycle Toolkit uses this runtime to run [KeptnTask](https://lifecycle.keptn.sh/docs/tasks/write-tasks/)
 for pre- and post-checks.