☁️ chore(automation): Applying changes from upstream repository.

Author: Megabyte Labs

.config/taskfiles/fix/Taskfile.yml

@@ -25,6 +25,9 @@ tasks:
       - :install:npm:eslint
       - :install:software:unbuffer
     desc: Fix ESLint errors automatically
+    vars:
+      ESLINT_LOG:
+        sh: mktemp
     summary: |
       # Fix Errors with ESLint Automatically
 
@@ -37,9 +40,6 @@ tasks:
 
       **Example fixing all files in a project:**
       `task fix:js`
-    vars:
-      ESLINT_LOG:
-        sh: mktemp
     log:
       error: ESLint found some issues that need to be fixed manually
       start: Auto-fixing with ESLint

.config/taskfiles/install/Taskfile-software.yml

@@ -597,15 +597,6 @@ tasks:
     status:
       - type git > /dev/null
 
-  git-issue:admin:
-    run: once
-    cmds:
-      - git clone https://github.com/dspinellis/git-issue.git .git-issue
-      - |
-        cd .git-issue
-        sudo make install
-      - rm -rf .git-issue
-
   gitlab-runner:
     run: once
     cmds:
@@ -620,6 +611,15 @@ tasks:
         vars:
           PACKAGE: gitleaks
 
+  git-issue:admin:
+    run: once
+    cmds:
+      - git clone https://github.com/dspinellis/git-issue.git .git-issue
+      - |
+        cd .git-issue
+        sudo make install
+      - rm -rf .git-issue
+
   glab:
     run: once
     cmds:

.config/taskfiles/release/Taskfile.yml

@@ -230,54 +230,24 @@ tasks:
 
   fail:
     deps:
-      - fail:ansible
-      - fail:docker
-      - fail:go
-      - fail:npm
-      - fail:packer
-      - fail:python
-    summary: |
-      | Command property | Description                                                                                                         |
-      |------------------|---------------------------------------------------------------------------------------------------------------------|
-      | `exit code`      | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-      | `stdout`         | Can be used for logging.                                                                                            |
-      | `stderr`         | Can be used for logging.                                                                                            |
-
-  fail:ansible:
-    cmds:
-      - 'true'
-    status:
-      - '[ -z "$RELEASE_ANSIBLE" ]'
-
-  fail:docker:
-    cmds:
-      - 'true'
-    status:
-      - '[ -z "$RELEASE_DOCKER" ]'
-
-  fail:go:
-    cmds:
-      - 'true'
-    status:
-      - '[ -z "$RELEASE_GO" ]'
-
-  fail:npm:
-    cmds:
-      - 'true'
-    status:
-      - '[ -z "$RELEASE_NPM" ]'
-
-  fail:packer:
-    cmds:
-      - 'true'
-    status:
-      - '[ -z "$RELEASE_PACKER" ]'
-
-  fail:python:
+      - :install:software:jq
+    env:
+      PACKAGE_JSON:
+        sh: jq -r '.' package.json
+      RELEASE_JSON:
+        sh: jq -r '.' .release.json
+      TMP:
+        sh: mktemp
+      VARIABLES_JSON:
+        sh: jq -r '.' .variables.json
     cmds:
-      - 'true'
+      - jq -n --arg pkg "$PACKAGE_JSON" --arg release "$RELEASE_JSON" --arg vars "$VARIABLES_JSON" --arg job "$CI_JOB_ID"
+        '.["package.json"] = $pkg | .[".release.json"] = $release | .[".variables.json"] = $vars | .CI_JOB_ID = $job' > "$TMP"
+      - >
+        curl -X POST -H "Content-Type: application/json" -d "$(cat "$TMP")"
+        "https://maker.ifttt.com/trigger/SemanticReleaseFail/json/with/key/$IFTTT_WEBHOOK_TOKEN"
     status:
-      - '[ -z "$RELEASE_PYTHON" ]'
+      - '[ -z "$IFTTT_WEBHOOK_TOKEN" ]'
 
   notes:
     cmds:
@@ -519,12 +489,6 @@ tasks:
   success:
     deps:
       - :install:software:jq
-    summary: |
-      | Command property | Description                                                                                                         |
-      |------------------|---------------------------------------------------------------------------------------------------------------------|
-      | `exit code`      | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
-      | `stdout`         | Can be used for logging.                                                                                            |
-      | `stderr`         | Can be used for logging.                                                                                            |
     env:
       PACKAGE_JSON:
         sh: jq -r '.' package.json
@@ -534,14 +498,20 @@ tasks:
         sh: mktemp
       VARIABLES_JSON:
         sh: jq -r '.' .variables.json
+    summary: |
+      | Command property | Description                                                                                                         |
+      |------------------|---------------------------------------------------------------------------------------------------------------------|
+      | `exit code`      | Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error. |
+      | `stdout`         | Can be used for logging.                                                                                            |
+      | `stderr`         | Can be used for logging.                                                                                            |
     cmds:
       - jq -n --arg pkg "$PACKAGE_JSON" --arg release "$RELEASE_JSON" --arg vars "$VARIABLES_JSON"
         '.["package.json"] = $pkg | .[".release.json"] = $release | .[".variables.json"] = $vars' > "$TMP"
       - >
         curl -X POST -H "Content-Type: application/json" -d "$(cat "$TMP")"
-        "https://maker.ifttt.com/trigger/SemanticRelease/json/with/key/$IFTTT_SEMANTICRELEASE"
+        "https://maker.ifttt.com/trigger/SemanticRelease/json/with/key/$IFTTT_WEBHOOK_TOKEN"
     status:
-      - '[ -z "$IFTTT_SEMANTICRELEASE" ]'
+      - '[ -z "$IFTTT_WEBHOOK_TOKEN" ]'
 
   verify:conditions:
     deps: