summaryrefslogtreecommitdiffstats
path: root/renovate.json
diff options
context:
space:
mode:
authorEarl Warren <contact@earl-warren.org>2024-04-11 10:59:40 +0200
committerEarl Warren <contact@earl-warren.org>2024-04-11 10:59:40 +0200
commitf672a63ae72f88b3398e06f59f3a68281de12bed (patch)
tree303d938800c573ce6a197df7f5ba7fe01eb7619a /renovate.json
parentMerge pull request '[TESTS] disable test failure on log.Error for now (part 2... (diff)
downloadforgejo-f672a63ae72f88b3398e06f59f3a68281de12bed.tar.xz
forgejo-f672a63ae72f88b3398e06f59f3a68281de12bed.zip
[RENOVATE] bitnami/minio upgrades are rare
It is used in the CI to verify the S3 backend works. It has no security or feature requirements and upgrading would only be required when a major version is published, which cannot be deduced from the version number. Making that upgrade available from the dashboard and dealt with when and if it gets the attention of a developer, even if once a year, is good enough.
Diffstat (limited to 'renovate.json')
-rw-r--r--renovate.json2
1 files changed, 1 insertions, 1 deletions
diff --git a/renovate.json b/renovate.json
index 0be6ebaa37..100f322dcd 100644
--- a/renovate.json
+++ b/renovate.json
@@ -26,7 +26,7 @@
},
{
"description": "Require dashboard approval for some deps",
- "matchDepNames": ["github.com/go-ap/activitypub"],
+ "matchDepNames": ["github.com/go-ap/activitypub", "bitnami/minio"],
"dependencyDashboardApproval": true
},
{