Cloned2Preserve
/
TrueChartsClone
mirror of https://github.com/truecharts/charts.git
1
0
Fork 0
Code

Commit released Helm Chart and docs for TrueCharts 

Signed-off-by: TrueCharts-Bot <bot@truecharts.org>
This commit is contained in:
TrueCharts-Bot 2021-12-05 23:30:28 +00:00
parent 87c8713fc8
commit bd8dc244fa
16 changed files with 420 additions and 6467 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
charts/stable/fireflyiii/CHANGELOG.md
View File

@ -1,6 +1,15 @@
# Changelog<br>
<a name="fireflyiii-13.0.10"></a>
### [fireflyiii-13.0.10](https://github.com/truecharts/apps/compare/fireflyiii-13.0.9...fireflyiii-13.0.10) (2021-12-05)
#### Chore
* fix some remaining issues after refactor work
<a name="fireflyiii-13.0.9"></a>
### fireflyiii-13.0.9 (2021-12-05)

2
charts/stable/fireflyiii/Chart.yaml
View File

@ -1,5 +1,5 @@
apiVersion: v2
appVersion: "5.5.12"
appVersion: "5.6.5"
dependencies:
- name: common
repository: https://truecharts.org

2
charts/stable/fireflyiii/helm-values.md
View File

@ -22,7 +22,7 @@ You will, however, be able to use all values referenced in the common chart here
| envValueFrom.DB_PASSWORD.secretKeyRef.name | string | `"dbcreds"` | |
| image.pullPolicy | string | `"IfNotPresent"` | |
| image.repository | string | `"tccr.io/truecharts/fireflyiii-core"` | |
| image.tag | string | `"version-5.5.12@sha256:f6dddfae65571d7995d5b24bf28fdf453775b825c35cac0c48b8ce52449090cf"` | |
| image.tag | string | `"v5.6.5@sha256:fe75d9df1daf62871eccb976643ff393ed1bd402b61baa0f17f7ad5289697264"` | |
| persistence.data.enabled | bool | `true` | |
| persistence.data.mountPath | string | `"/var/www/html/storage/upload"` | |
| podSecurityContext.runAsGroup | int | `0` | |

422
charts/stable/fireflyiii/security.md
View File

File diff suppressed because one or more lines are too long

9
charts/stable/gitea/CHANGELOG.md
View File

@ -1,6 +1,15 @@
# Changelog<br>
<a name="gitea-5.0.11"></a>
### [gitea-5.0.11](https://github.com/truecharts/apps/compare/gitea-5.0.10...gitea-5.0.11) (2021-12-05)
#### Chore
* fix some remaining issues after refactor work
<a name="gitea-5.0.10"></a>
### gitea-5.0.10 (2021-12-05)

2
charts/stable/gitea/helm-values.md
View File

@ -20,7 +20,7 @@ You will, however, be able to use all values referenced in the common chart here
| envFrom[0].configMapRef.name | string | `"gitea-env"` | |
| image.pullPolicy | string | `"IfNotPresent"` | |
| image.repository | string | `"tccr.io/truecharts/gitea"` | |
| image.tag | string | `"v1.15.7-rootless"` | |
| image.tag | string | `"v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf"` | |
| initContainers.1-init-directories.command[0] | string | `"/usr/sbin/init_directory_structure.sh"` | |
| initContainers.1-init-directories.envFrom[0].configMapRef.name | string | `"gitea-env"` | |
| initContainers.1-init-directories.image | string | `"{{ .Values.image.repository }}:{{ .Values.image.tag }}"` | |

11
charts/stable/gitea/security.md
View File

@ -61,6 +61,9 @@ hide:
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | <details><summary>Expand...</summary> &#39;runAsNonRoot&#39; forces the running image to run as a non-root user to ensure least privileges. <br> <hr> <br> Container &#39;2-configure-gitea&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.runAsNonRoot&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted">https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted</a><br><a href="https://avd.aquasec.com/appshield/ksv012">https://avd.aquasec.com/appshield/ksv012</a><br></details> |
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | <details><summary>Expand...</summary> &#39;runAsNonRoot&#39; forces the running image to run as a non-root user to ensure least privileges. <br> <hr> <br> Container &#39;autopermissions&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.runAsNonRoot&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted">https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted</a><br><a href="https://avd.aquasec.com/appshield/ksv012">https://avd.aquasec.com/appshield/ksv012</a><br></details> |
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | <details><summary>Expand...</summary> &#39;runAsNonRoot&#39; forces the running image to run as a non-root user to ensure least privileges. <br> <hr> <br> Container &#39;postgresql-init&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.runAsNonRoot&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted">https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted</a><br><a href="https://avd.aquasec.com/appshield/ksv012">https://avd.aquasec.com/appshield/ksv012</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;1-init-directories&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;2-configure-gitea&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;RELEASE-NAME-gitea&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;autopermissions&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;postgresql-init&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | <details><summary>Expand...</summary> An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk. <br> <hr> <br> Container &#39;1-init-directories&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.readOnlyRootFilesystem&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/">https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/</a><br><a href="https://avd.aquasec.com/appshield/ksv014">https://avd.aquasec.com/appshield/ksv014</a><br></details> |
@ -95,9 +98,9 @@ hide:
tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
tccr.io/truecharts/postgresql:v14.1.0@sha256:4816fcc7f4f3a5a6db13aa70aa3d374fec33e096051be22db6a72d96cf2d8da1
'tccr.io/truecharts/gitea:v1.15.7-rootless'
'tccr.io/truecharts/gitea:v1.15.7-rootless'
tccr.io/truecharts/gitea:v1.15.7-rootless
'tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf'
'tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf'
tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf
tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
tccr.io/truecharts/memcached:v1.6.12@sha256:9e89ba2ea066867abaeacb2357d6a1f3b82e18898520c2f438a6b915b2409b79
tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
@ -358,7 +361,7 @@ hide:
#### Container: tccr.io/truecharts/gitea:v1.15.7-rootless (alpine 3.13.7)
#### Container: tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf (alpine 3.13.7)
**alpine**

9
charts/stable/grocy/CHANGELOG.md
View File

@ -1,6 +1,15 @@
# Changelog<br>
<a name="grocy-9.0.19"></a>
### [grocy-9.0.19](https://github.com/truecharts/apps/compare/grocy-9.0.18...grocy-9.0.19) (2021-12-05)
#### Chore
* fix some remaining issues after refactor work
<a name="grocy-9.0.18"></a>
### grocy-9.0.18 (2021-12-05)

9
docs/apps/stable/fireflyiii/CHANGELOG.md
View File

@ -1,6 +1,15 @@
# Changelog<br>
<a name="fireflyiii-13.0.10"></a>
### [fireflyiii-13.0.10](https://github.com/truecharts/apps/compare/fireflyiii-13.0.9...fireflyiii-13.0.10) (2021-12-05)
#### Chore
* fix some remaining issues after refactor work
<a name="fireflyiii-13.0.9"></a>
### fireflyiii-13.0.9 (2021-12-05)

2
docs/apps/stable/fireflyiii/helm-values.md
View File

@ -22,7 +22,7 @@ You will, however, be able to use all values referenced in the common chart here
| envValueFrom.DB_PASSWORD.secretKeyRef.name | string | `"dbcreds"` | |
| image.pullPolicy | string | `"IfNotPresent"` | |
| image.repository | string | `"tccr.io/truecharts/fireflyiii-core"` | |
| image.tag | string | `"version-5.5.12@sha256:f6dddfae65571d7995d5b24bf28fdf453775b825c35cac0c48b8ce52449090cf"` | |
| image.tag | string | `"v5.6.5@sha256:fe75d9df1daf62871eccb976643ff393ed1bd402b61baa0f17f7ad5289697264"` | |
| persistence.data.enabled | bool | `true` | |
| persistence.data.mountPath | string | `"/var/www/html/storage/upload"` | |
| podSecurityContext.runAsGroup | int | `0` | |

422
docs/apps/stable/fireflyiii/security.md
View File

File diff suppressed because one or more lines are too long

9
docs/apps/stable/gitea/CHANGELOG.md
View File

@ -1,6 +1,15 @@
# Changelog<br>
<a name="gitea-5.0.11"></a>
### [gitea-5.0.11](https://github.com/truecharts/apps/compare/gitea-5.0.10...gitea-5.0.11) (2021-12-05)
#### Chore
* fix some remaining issues after refactor work
<a name="gitea-5.0.10"></a>
### gitea-5.0.10 (2021-12-05)

2
docs/apps/stable/gitea/helm-values.md
View File

@ -20,7 +20,7 @@ You will, however, be able to use all values referenced in the common chart here
| envFrom[0].configMapRef.name | string | `"gitea-env"` | |
| image.pullPolicy | string | `"IfNotPresent"` | |
| image.repository | string | `"tccr.io/truecharts/gitea"` | |
| image.tag | string | `"v1.15.7-rootless"` | |
| image.tag | string | `"v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf"` | |
| initContainers.1-init-directories.command[0] | string | `"/usr/sbin/init_directory_structure.sh"` | |
| initContainers.1-init-directories.envFrom[0].configMapRef.name | string | `"gitea-env"` | |
| initContainers.1-init-directories.image | string | `"{{ .Values.image.repository }}:{{ .Values.image.tag }}"` | |

11
docs/apps/stable/gitea/security.md
View File

@ -61,6 +61,9 @@ hide:
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | <details><summary>Expand...</summary> &#39;runAsNonRoot&#39; forces the running image to run as a non-root user to ensure least privileges. <br> <hr> <br> Container &#39;2-configure-gitea&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.runAsNonRoot&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted">https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted</a><br><a href="https://avd.aquasec.com/appshield/ksv012">https://avd.aquasec.com/appshield/ksv012</a><br></details> |
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | <details><summary>Expand...</summary> &#39;runAsNonRoot&#39; forces the running image to run as a non-root user to ensure least privileges. <br> <hr> <br> Container &#39;autopermissions&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.runAsNonRoot&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted">https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted</a><br><a href="https://avd.aquasec.com/appshield/ksv012">https://avd.aquasec.com/appshield/ksv012</a><br></details> |
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | <details><summary>Expand...</summary> &#39;runAsNonRoot&#39; forces the running image to run as a non-root user to ensure least privileges. <br> <hr> <br> Container &#39;postgresql-init&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.runAsNonRoot&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted">https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted</a><br><a href="https://avd.aquasec.com/appshield/ksv012">https://avd.aquasec.com/appshield/ksv012</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;1-init-directories&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;2-configure-gitea&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;RELEASE-NAME-gitea&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;autopermissions&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV013 | Image tag &#39;:latest&#39; used | LOW | <details><summary>Expand...</summary> It is best to avoid using the &#39;:latest&#39; image tag when deploying containers in production. Doing so makes it hard to track which version of the image is running, and hard to roll back the version. <br> <hr> <br> Container &#39;postgresql-init&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should specify an image tag </details>| <details><summary>Expand...</summary><a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images">https://kubernetes.io/docs/concepts/configuration/overview/#container-images</a><br><a href="https://avd.aquasec.com/appshield/ksv013">https://avd.aquasec.com/appshield/ksv013</a><br></details> |
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | <details><summary>Expand...</summary> An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk. <br> <hr> <br> Container &#39;1-init-directories&#39; of Deployment &#39;RELEASE-NAME-gitea&#39; should set &#39;securityContext.readOnlyRootFilesystem&#39; to true </details>| <details><summary>Expand...</summary><a href="https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/">https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/</a><br><a href="https://avd.aquasec.com/appshield/ksv014">https://avd.aquasec.com/appshield/ksv014</a><br></details> |
@ -95,9 +98,9 @@ hide:
tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
tccr.io/truecharts/postgresql:v14.1.0@sha256:4816fcc7f4f3a5a6db13aa70aa3d374fec33e096051be22db6a72d96cf2d8da1
'tccr.io/truecharts/gitea:v1.15.7-rootless'
'tccr.io/truecharts/gitea:v1.15.7-rootless'
tccr.io/truecharts/gitea:v1.15.7-rootless
'tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf'
'tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf'
tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf
tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
tccr.io/truecharts/memcached:v1.6.12@sha256:9e89ba2ea066867abaeacb2357d6a1f3b82e18898520c2f438a6b915b2409b79
tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c
@ -358,7 +361,7 @@ hide:
#### Container: tccr.io/truecharts/gitea:v1.15.7-rootless (alpine 3.13.7)
#### Container: tccr.io/truecharts/gitea:v1.15.7@sha256:76b30ee8446e878c88618a69e73431890b66aa65e484261b4e0b6dd5f23cbebf (alpine 3.13.7)
**alpine**

9
docs/apps/stable/grocy/CHANGELOG.md
View File

@ -1,6 +1,15 @@
# Changelog<br>
<a name="grocy-9.0.19"></a>
### [grocy-9.0.19](https://github.com/truecharts/apps/compare/grocy-9.0.18...grocy-9.0.19) (2021-12-05)
#### Chore
* fix some remaining issues after refactor work
<a name="grocy-9.0.18"></a>
### grocy-9.0.18 (2021-12-05)

5957
docs/index.yaml
View File

File diff suppressed because it is too large Load Diff