chore(deps): update homeassistant/home-assistant docker tag to v2025

.drone.yml

@@ -17,7 +17,7 @@ steps:
 - name: helm lint
   commands:
   - helm lint
-  image: git.cryptic.systems/volker.raschek/helm:3.19.2
+  image: git.cryptic.systems/volker.raschek/helm:3.17.1
   resources:
     limits:
       cpu: 50
@@ -35,7 +35,7 @@ steps:
 - name: helm template
   commands:
   - helm template .
-  image: git.cryptic.systems/volker.raschek/helm:3.19.2
+  image: git.cryptic.systems/volker.raschek/helm:3.17.1
   resources:
     limits:
       cpu: 150
@@ -53,7 +53,7 @@ steps:
       from_secret: smtp_username
     SMTP_PASSWORD:
       from_secret: smtp_password
-  image: git.cryptic.systems/volker.raschek/drone-email:0.2.0
+  image: git.cryptic.systems/volker.raschek/drone-email:0.1.5
   resources:
     limits:
       cpu: 150
@@ -93,7 +93,7 @@ steps:
       from_secret: helm_repo_password
     HELM_REPO_USERNAME:
       from_secret: helm_repo_username
-  image: git.cryptic.systems/volker.raschek/helm:3.19.2
+  image: git.cryptic.systems/volker.raschek/helm:3.17.1
   resources:
     limits:
       cpu: 150

.markdownlint.yaml

@@ -45,9 +45,9 @@ MD012:
 # MD013/line-length - Line length
 MD013:
   # Number of characters
-  line_length: 120
+  line_length: 80
   # Number of characters for headings
-  heading_line_length: 120
+  heading_line_length: 80
   # Number of characters for code blocks
   code_block_line_length: 80
   # Include code blocks
@@ -56,6 +56,8 @@ MD013:
   tables: false
   # Include headings
   headings: true
+  # Include headings
+  headers: true
   # Strict length checking
   strict: false
   # Stern length checking
@@ -71,7 +73,7 @@ MD022:
 # MD024/no-duplicate-heading/no-duplicate-header - Multiple headings with the same content
 MD024:
   # Only check sibling headings
-  siblings_only: true
+  allow_different_nesting: true
 
 # MD025/single-title/single-h1 - Multiple top-level headings in the same document
 MD025:
@@ -126,21 +128,8 @@ MD041:
 # MD044/proper-names - Proper names should have the correct capitalization
 MD044:
   # List of proper names
-  names:
+  # names:
-    - Git
+  # - drone
-    - GitDevOps
-    - Gitea
-    - GitHub
-    - GitLab
-    - GitOps
-    - kube-prometheus-stack
-    - Memcached
-    - Oracle
-    - PostgreSQL
-    - Prometheus
-    - prometheus-exporter
-    - SSL
-    - TLS
   # Include code blocks
   code_blocks: false
 

.markdownlintignore

@@ -1,4 +0,0 @@
-.github/
-Chart.lock
-charts/
-node_modules/

Chart.yaml

@@ -3,7 +3,7 @@ name: homeassistant
 description: Helm chart for homeassistant
 type: application
 version: "0.1.0"
-appVersion: "2023.12.4"
+appVersion: "2025.10.2"
 icon: https://upload.wikimedia.org/wikipedia/commons/6/6e/Home_Assistant_Logo.svg
 
 keywords:

README.md

@@ -4,7 +4,8 @@
 
 This is a helm chart for [homeassistant](https://github.com/morpheus65535/homeassistant/).
 
-This helm chart can be found on [artifacthub.io](https://artifacthub.io/) and can be installed via helm.
+This helm chart can be found on [artifacthub.io](https://artifacthub.io/) and
+can be installed via helm.
 
 ```bash
 helm repo add volker.raschek https://charts.cryptic.systems/volker.raschek
@@ -15,13 +16,16 @@ helm install homeassistant volker.raschek/homeassistant
 
 ### Mountpoints
 
-As default all configuration and media files will be stored inside the container filesystem. Inside the `values.yaml`
+As default all configuration and media files will be stored inside the container
-files the sections `volumes` and `volumeMounts` to mount additional volumes inside the container. For example to mount
+filesystem. Inside the `values.yaml` files the sections `volumes` and
-the directories containing configuration and media files on separate mountpoints. The `values.yaml` contains also some
+`volumeMounts` to mount additional volumes inside the container. For example to
-examples to mount the directories inside the host filesystem.
+mount the directories containing configuration and media files on separate
+mountpoints. The `values.yaml` contains also some examples to mount the
+directories inside the host filesystem.
 
 #### Troubleshooting
 
-The application use as backend a sqlite database. If the database is stored on a network filesystem like nfs, it is
+The application use as backend a sqlite database. If the database is stored on a
-quite possible that the application lacks or is unusable, because sqlite is not designed to be used as a database
+network filesystem like nfs, it is quite possible that the application lacks or
-accesses over network.
+is unusable, because sqlite is not designed to be used as a database accesses
+over network.