diff --git a/index.yaml b/index.yaml
index cff2b580..73b1dd52 100644
--- a/index.yaml
+++ b/index.yaml
@@ -55089,6 +55089,64 @@ entries:
     - https://github.com/saritasa-nest/saritasa-devops-helm-charts/releases/download/saritasa-tekton-apps-0.1.0/saritasa-tekton-apps-0.1.0.tgz
     version: 0.1.0
   saritasa-tekton-pipelines:
+  - apiVersion: v2
+    created: "2023-07-06T13:18:59.377894671Z"
+    dependencies:
+    - condition: saritasa-tekton.enabled
+      name: saritasa-tekton
+      repository: https://saritasa-nest.github.io/saritasa-devops-helm-charts/
+      version: ~0.1.x
+    description: 'A Helm chart for Tekton Pipelines  Implements: - common tekton tasks
+      - common tekton pipelines - common tekton trigger templates - common tekton
+      trigger bindings  Implemented pipelines include: - buildpack based pipelines
+      based on generator template (php, python, frontend, nodejs, ruby, go) - kaniko
+      pipeline - wordpress pipeline  ## `example usage with argocd`  Install the chart:  ```
+      helm repo add saritasa https://saritasa-nest.github.io/saritasa-devops-helm-charts/
+      ```  then if you want to support only frontend and django pipelines based on
+      buildpack without any script modifications:  ```yaml apiVersion: argoproj.io/v1alpha1
+      kind: Application metadata:   name: tekton-pipelines   namespace: argo-cd   finalizers:   -
+      resources-finalizer.argocd.argoproj.io   annotations:     argocd.argoproj.io/sync-options:
+      SkipDryRunOnMissingResource=true     argocd.argoproj.io/sync-wave: "60" spec:   destination:     server:
+      https://kubernetes.default.svc     namespace: ci   project: default   source:     chart:
+      saritasa-tekton-pipelines     helm:       values: |         buildpacks:           enabled:
+      true           generate:             buildpackFrontendBuildPipeline:               enabled:
+      true              buildpackDjangoBuildPipeline:               enabled: true      repoURL:
+      https://saritasa-nest.github.io/saritasa-devops-helm-charts/     targetRevision:
+      "0.1.4"   syncPolicy:     automated:       prune: true       selfHeal: true     syncOptions:       -
+      CreateNamespace=true ```  If you want to modify the behavior of the build step
+      you can easily do that by redefining steps you want to run prior to running
+      the `build` step of the associated buildpack pipeline. You can create multiple
+      versions of pipelines as a result. Just make sure to give them a different name  an
+      example:  ```yaml buildpacks:   enabled: true   generate:     buildpackFrontendBuildPipelineNew:       name:
+      buildpack-frontend-build-pipeline-new       enabled: false       buildTaskName:
+      buildpack-frontend-new       buildTaskSteps:         - name: hello1           image:
+      node:16           imagePullPolicy: IfNotPresent           workingDir: $(resources.inputs.app.path)           script:
+      |             #!/bin/bash             echo "hello world1"          - name: hello2           image:
+      node:16           imagePullPolicy: IfNotPresent           workingDir: $(resources.inputs.app.path)           script:
+      |             #!/bin/bash             echo "hello world2" ```  If you want to
+      modify Kaniko build arguments, you can pass `kaniko_extra_args` parameter to
+      `kaniko-pipeline`. For example, if you want to pass `BASE_IMAGE` build argument
+      value to be used in Dockerfile you can add following line to specific project
+      trigger-binding: ```yaml - name: kaniko_extra_args   value: --build-arg=BASE_IMAGE=965067289393.dkr.ecr.us-west-2.amazonaws.com/saritasa/legacy/php:php71-smart-screen-base
+      ```  Chart has possibility to perform `Sentry` releases if it is needed, you
+      can configure it by updating below settings in values.yaml:  ```yaml sentry:   enabled:
+      true   authTokenSecret: "sentry-auth-token"  # auth token to connect to Sentry
+      API (change it if you have custom value)   authTokenSecretKey: "auth-token"      #
+      key for auth token in `authTokenSecret` secret (change it if you have custom
+      value)   org: "saritasa"                       # name of your Sentry organization
+      (change it if you have custom value)   url: https://sentry.saritasa.rocks/   #
+      Sentry url (change it if you have custom value) ```  After configuring these
+      values, you will have an extra `sentry-release` step after `argocd-deploy` one
+      for buildpacks and kaniko builds. '
+    digest: f3f4bc5818ee3b858e81d0020bace1e25f020bad4608bab5ce4f4277f22129aa
+    maintainers:
+    - name: Saritasa
+      url: https://www.saritasa.com/
+    name: saritasa-tekton-pipelines
+    type: application
+    urls:
+    - https://github.com/saritasa-nest/saritasa-devops-helm-charts/releases/download/saritasa-tekton-pipelines-0.1.37-dev.2/saritasa-tekton-pipelines-0.1.37-dev.2.tgz
+    version: 0.1.37-dev.2
   - apiVersion: v2
     created: "2023-07-06T08:57:33.202658385Z"
     dependencies:
@@ -62922,4 +62980,4 @@ entries:
     urls:
     - https://github.com/saritasa-nest/saritasa-devops-helm-charts/releases/download/terraform-pod-0.0.1/terraform-pod-0.0.1.tgz
     version: 0.0.1
-generated: "2023-07-06T08:57:33.203843695Z"
+generated: "2023-07-06T13:18:59.379327588Z"