Update to 2021-10-22 10:00

3 years ago · ce1f7f65dd
parent a20e2e2c6f
commit ce1f7f65dd
2 changed files with 4 additions and 4 deletions
--- a/roles/gitea/defaults/main.yml
+++ b/roles/gitea/defaults/main.yml
@ -1,11 +1,11 @@
 ---

 # Version to install
-gitea_version: 1.15.4
+gitea_version: 1.15.5
 # URL to the binary
 gitea_bin_url: https://dl.gitea.io/gitea/{{ gitea_version }}/gitea-{{ gitea_version }}-linux-amd64
 # sha256 of the binary
-gitea_bin_sha256: 1a7ccaa7856ea992cd4dc584086158b13bec43a01a8e8b45e874bf7dac6b2175
+gitea_bin_sha256: c3f190848c271bf250d385b80c1a98a7e2c9b23d092891cf1f7e4ce18c736484
 # Handle updates. If set to false, ansible will only install
 # Gitea and then won't touch an existing installation
 gitea_manage_upgrade: True
--- a/roles/metabase/defaults/main.yml
+++ b/roles/metabase/defaults/main.yml
@ -1,11 +1,11 @@
 ---

 # Version to deploy
-metabase_version: 0.41.0
+metabase_version: 0.41.1
 # URL to fetch the jar
 metabase_jar_url: https://downloads.metabase.com/v{{ metabase_version }}/metabase.jar
 # Expected sha1 of the jar
-metabase_jar_sha256: f2407e5f9d161ae35549e8a7932c18f9d54f97924a71c55b324a4ba68dd40290
+metabase_jar_sha256: 8a222bf5b255dc80eb783a85b003b44835e24b739ae9e110e1ba0f583d86fd42
 # Should ansible handle upgrades ? If set to false, only the initial install (and the config) will be handled
 metabase_manage_upgrade: True