renovate: name the nginx alpine check in #84 accurately
The rationale called the alpine switch a proposal from the issue text. A later comment on #84 commissions it as a check with a defined scope (nginx.conf compatibility, port 8080, uid 101, /tmp redirection) to be done alongside the seccompProfile PR for this chart. The outcome is open, the check is not - the constraint has to survive either way.
This commit is contained in:
2 files changed
+4
-3
No files matched your search
+3
-2
@@ -108,8 +108,9 @@
|
||||
matchDatasources: ["docker"],
|
||||
matchPackageNames: ["nginx", "library/nginx", "docker.io/library/nginx"],
|
||||
// Even minor: any minor whose last digit is even, so 1.30.x passes and
|
||||
// 1.31.x does not. The trailing (-.+)? is load-bearing: #84 proposes
|
||||
// moving this sidecar to a slimmer base image, and with a variant tag
|
||||
// 1.31.x does not. The trailing (-.+)? is load-bearing: #84 commissioned
|
||||
// a check on moving this sidecar to 1.30.4-alpine (outcome open, to be
|
||||
// done alongside the seccompProfile PR), and with a variant tag
|
||||
// like 1.30.4-alpine docker versioning only ever offers candidates
|
||||
// carrying the same suffix. Without the optional suffix, every one of
|
||||
// them would fail this filter and nginx would silently stop receiving
|
||||
|
||||
Reference in new issue
Block a user